Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnknownAdapter and node_modules #3006

Closed
isuvorov opened this issue Jun 8, 2015 · 3 comments
Closed

UnknownAdapter and node_modules #3006

isuvorov opened this issue Jun 8, 2015 · 3 comments

Comments

@isuvorov
Copy link

isuvorov commented Jun 8, 2015

I use Docker structure like this https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/05-nginx-express-redis-nodemon

/src/package.json - copy of package.json
/src/node_modules - all dependencies
/src/app - Sails app

All work fine, but there some trouble:

https://github.com/balderdashy/sails/blob/74a822aa6744cce9600b65f21bbd8f087413bbe8/lib/hooks/orm/backwards-compatibility/upgrade-datastore.js
// Before trying to actually require the adapter, make sure we know the real module path:
var node_modules = path.resolve(sails.config.appPath, 'node_modules');

I think, Sails try to find adapter in /src/app/node_modules
How can it fix?

@jdcauley
Copy link
Contributor

@isuvorov

Why do you have your node_modules in an alternate directory? Out of curiosity.

I may be wrong but you may be able to define this in the sailsrc file

@kevinburkeshyp
Copy link

This is a dupe of #2505, since module paths are hard coded in Sails there's currently no way around this besides symlinking the node_modules folder into the "right" place.

@sailsbot
Copy link

Thanks for posting, @isuvorov. I'm a repo bot-- nice to meet you!

It has been 60 days since there have been any updates or new comments on this page. If this issue has been resolved, feel free to disregard the rest of this message. On the other hand, if you are still waiting on a patch, please:

  • review our contribution guide to make sure this submission meets our criteria (only verified bugs with documented features, please; no questions, commentary, or bug reports about undocumented features or unofficial plugins)
  • create a new issue with the latest information, including updated version details with error messages, failing tests, and a link back to the original issue. This allows GitHub to automatically create a back-reference for future visitors arriving from search engines.

Thanks so much for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants