Resource copying can be confusing for resource developers about resource HOT 3 CLOSED

bumping this issue, as it continues to be annoying. it's why @wolfbiter and i have had to make silly files like https://github.com/bigcompany/resources/blob/master/bitcoin/test/test and https://github.com/bigcompany/resources/blob/master/view/test/test for running our tests. i like the idea of detecting if we are inside require.resolve('resources') and not using the cache, but an option in the resource singleton would also work because we could always set it on the resource var in tests before .use()-ing any resources.

from resource.

Related: bigcompany/resources#14

from resource.

so if all the resources are on npm, then resource.use() can download each resource as an npm module, live like any big dependency. this means getting rid of 'resources' as a collection, as each resource is independent. also this keeps resource development separate and distinct from app development, should solve this issue and problem of having to sudo npm link && npm link resources when developing resources. within a resource directory, resource.use() should to have access to that resource, such as in resource tests.

if you can work on adding this functionality to 'resource' i'd be happy to work on getting 'resources' onto npm.

from resource.