-
-
Notifications
You must be signed in to change notification settings - Fork 333
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
Latest master branch does not build #349
Comments
We may need to check the npm version we're running in? It's sad to need to do that in 2016. |
It's this line:
This builds correctly in my project with npm 3.x but that should not matter. The only difference I can see at a glance is that I added ember-paper to dependencies instead of devDependencies, but that really shouldn't matter. Also it's builds on travis, which uses npm 2.x so this does seem odd. I'll take a closer look though |
A good smoke test, and way to work backwards is to run |
Same error after npm linking as well. |
@cah-danmonroe - we can pair if you'd like - try the following first though inside your project directory:
The problem seems to be that there is no folder
Make sure to use npm 3.x with node 4.x. Let me know if your still stuck. Don't mind jumping on screenhero for a sec |
If I switch to npm 3.8.6 with node 5.11.0, ember paper does build. It puts angular-material-source into my project's node_modules directory. npm version 2.x does not. |
Glad you got it working. Sorry about the trouble. Node 0.12 and npm 2.x on my machine do work, and so does travis which makes this all a bit interesting. We'll see if it arises again. Thanks for reporting the issue @cah-danmonroe |
@eriktrom From what I understand, the problem was not building ember-paper but installing ember-paper. |
I think the issue still exists. It never worked for me when I was on npm 2.147/node 4.23. I had to upgrade for it to work. If your intention is to support npm 2.x, then I think there is more to investigate. |
I had the same issue when running node 4.4.3 and npm 2.15.1. Upgrading to npm 3.x resolves the issue, but as ember-cli recommends npm 2.x it would be nice if this could be fixed. |
thanks for letting me know, im looking further into it (now im pretty curious) |
- Angular-material-source does not have a main node module, its only built to ./dist and published via bower. The first attempt to make this work with npm 3.x broke (some users) npm 2.x env's. - This aims to allow building a project that includes this addon for npme 2.x and 3.x for all versions of node. fixes adopted-ember-addons#349
Did a little digging, understand the problem better, made my best attempt in #364 Need ya'll to try it, works on my machine, but it always has, LOL |
Closing in favor of discussion in PR #346. |
- Angular-material-source does not have a main node module, its only built to ./dist and published via bower. The first attempt to make this work with npm 3.x broke (some users) npm 2.x env's. - This aims to allow building a project that includes this addon for npme 2.x and 3.x for all versions of node. fixes #349
- Angular-material-source does not have a main node module, its only built to ./dist and published via bower. The first attempt to make this work with npm 3.x broke (some users) npm 2.x env's. - This aims to allow building a project that includes this addon for npme 2.x and 3.x for all versions of node. fixes adopted-ember-addons#349
Installing the latest master branch fails to build.
npm --version
ember --version
Here are the steps I took to reproduce:
package.json:
bower.json:
The text was updated successfully, but these errors were encountered: