Closed Bug 1027717 Opened 10 years ago Closed 10 years ago

Use a package manager to manage calendar app dependencies


(Firefox OS Graveyard :: Gaia::Calendar, defect)

Not set


(Not tracked)

2.0 S4 (20june)


(Reporter: gaye, Unassigned)



(Whiteboard: [priority][p=2])


(1 file, 1 obsolete file)

Currently, we copy all of our dependencies which are developed outside of gaia into the gaia tree for lack of a better dependency management situation. We should take advantage of a nice, existing tool like npm, bower, or component to do the dependency management for us. We probably still have to check our node_modules/, bower_components/, or whatever else folder into source control since we have build and testing restrictions, but I think it's still a step in the right direction.

Since the way that many use bower is to

(1) distribute build artifacts like html / js binaries / css without extra library and test code and
(2) put artifacts in the top-level directory to make urls less complicated

I suggest bower. It's also quite popular amongst frontend people so many useful libraries are published in the bower registry.
Blocks: 1027729
Whiteboard: [priority]
Would like to push ahead here and also with requirejs but want to make sure we have consensus :)
Flags: needinfo?(mmedeiros)
Flags: needinfo?(jlal)
Sounds good as long as we don't regress performance (I am sure we can improve it somehow with better rjs tooling)
Flags: needinfo?(jlal)
I agree that having something (anything) would be good. I really like the simplicity and flexibility of volo[1] (by James Burke) since we can pick a single file and tell where it should be installed and the info is stored on the package.json. - I think it plays well with AMD and non-AMD code, for me it still feels weird to use npm to require code that is not written in the node.js module format. But I would be OK with any choice.

Flags: needinfo?(mmedeiros)
Hey Miller,

I've gone ahead and packaged up our caldav and ical libraries for bower and registered them. node-uuid and page.js were already published in the registry. There's a lot of noise here, but largely not much has changed. I went ahead and updated the code in js/ and test/ to point to the new library locations.
Attachment #8443114 - Flags: review?(mmedeiros)
Whiteboard: [priority] → [priority][p=2]
Second try using volo which has a much smaller footprint on our project.
Attachment #8443114 - Attachment is obsolete: true
Attachment #8443114 - Flags: review?(mmedeiros)
Attachment #8443627 - Flags: review?(mmedeiros)
Comment on attachment 8443627 [details] [review]
Link to Github pull-request:

volo FTW!
Attachment #8443627 - Flags: review?(mmedeiros) → review+ landed on master
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S4 (20june)
See Also: → 1036753
You need to log in before you can comment on or make changes to this bug.