-
Notifications
You must be signed in to change notification settings - Fork 38
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
Yarn workspaces #78
Comments
|
Luckily, until this is resolved, the solution is to just remove ember-cli-dependency-checker. 🙃 |
ef4
added a commit
to ef4/ember-cli-dependency-checker
that referenced
this issue
Nov 14, 2017
This fixes quaertym#78 and removes a deprecation warning in ember-cli master (`DEPRECATION: An addon is trying to access project.nodeModulesPath. This is not a reliable way to discover npm modules....`).
ef4
added a commit
to ef4/ember-cli-dependency-checker
that referenced
this issue
Nov 14, 2017
This fixes quaertym#78 and removes a deprecation warning in ember-cli master (`DEPRECATION: An addon is trying to access project.nodeModulesPath. This is not a reliable way to discover npm modules....`).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, it doesn't work correctly with Yarn workspaces... Here is the issues: yarnpkg/yarn#4503 (same as yarnpkg/yarn#4081). All other apps works fine, they search for
node_modules
in root dir instead of current dir if they don't find it, but Ember just search it in current dir...The text was updated successfully, but these errors were encountered: