local dependencies

[David Moshal]

apologies if this is a duplicate, but I can't find the answer in the docs.

assuming an app with multiple components.

assume that these components have shared dependencies.
as an example, assume each component depends on bootstrap 3.

Questions:

1. do I have to install bootstrap 3 in every component, ie will every component have a components directory with bootstrap 3? (and if so, what's the best way to update all these).

2. is it possible to create a common local /components directory which can be referenced, and updated once?

3. is it possible to create multiple components in a single directory?

Thanks

David

[David Moshal]

I guess I'm asking for clarity on the 'local' and 'path' settings of component.json
David

[Ian Storm Taylor]

Check out the component.io repo for an example of this in action. Basically throw all your components in /lib and then add that to your paths. And then you can component install from the root folder and all of the dependencies will end up  in /components.

Ian

--
You received this message because you are subscribed to the Google Groups "component" group.
To unsubscribe from this group and stop receiving emails from it, send an email to componentjs...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Amjad Masad]

1. do I have to install bootstrap 3 in every component, ie will every component have a components directory with bootstrap 3? (and if so, what's the best way to update all these).

In addition to what Ian said, you can either add a package as a dependency for every component using it and just do require('packageName') or can add it in the root component.json but should then qualify the full name when requiring: require('../username-packageName'). The former is preferred.

3. is it possible to create multiple components in a single directory?

yep, as long as each in a sub directory.

[Zachary Adam Kaplan]

the only weird part for me is:

* why is index.js not referenced as the `main` or in the `scripts` property of it's own component.json? 

see https://github.com/component/component.io/blob/0b25689c302a6b70ee1b35a13f0c62a8e42c53b6/lib/boot/component.json#L16

[Ian Storm Taylor]

index.js in that case is a node file instead of a component file. We’ve run into this confusion as well, and have considered calling our stuff browser and server very explicitly to make it more obvious. So you’d end up with a structure like:

/

  browser/

  server/

  browser.js

  component.json

  package.json

  server.js

Instead of a single shared /lib you just end up with two named /browser and /server for paths.  

--

[Amjad Masad]

We've taken a different approach here https://github.com/max99x/guesshub/

The server is called backend/ and component app is called app/. In our case the server is written in Python