Default install of big throws on missing modules

[luk-]

I installed big in a local node_modules folder and started a webserver just using the admin resource. It threw errors for missing both resource & resources modules.

[Marak]

Well that's not good. They use to be listed as regular dependencies but now are peerDependencies as per 9769f8c

I don't think this is the correct usage of peerDependencies

[luk-]

I don't think this is the correct usage of peerDependencies

I agree with this.

[erobit]

The error is being thrown for me when executing my /app/index.js file. At this point, any /app/node_modules/big/node_modules/resources that are used in the file are copied to the /app/resources/ folder. The copied resources, cannot resolve the require('resource') package (installed by default as big dependencies) if the resource/resources packages haven't been manually installed through npm install resource / npm install resources.

I'm not sure if this is by design, with the assumption that big is to be installed as a global module. I wasn't able to get big to work as a global module, but it could have been due to NODE_PATH issues or other.

I guess for the time being, the documentation could be updated (How to create a big app?) to indicate that along with big installed globally, resource and resources need to be installed when creating a new app.

[Marak]

Big no now zero-lines long. require('resource') is now used instead