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

aurelia cli does not run after installing dependency from npm #826

Closed
monis01 opened this issue Feb 15, 2018 · 11 comments
Closed

aurelia cli does not run after installing dependency from npm #826

monis01 opened this issue Feb 15, 2018 · 11 comments

Comments

@monis01
Copy link

monis01 commented Feb 15, 2018

I'm submitting a bug report

  • Library Version:
    0.32.0

Please tell us about your environment:

  • Operating System:
    Linux (Ubuntu 16.04)

  • Node Version:
    8.6.0

  • NPM Version:
    5.6.0

  • Language:
    ESNext

Current behavior:
(I am following the contact manager example from the contact-manager )
All working good til the point I got plugin.load error, after little debugging found out bootstrap is not present in node_modules. So I stopped the application and npm install bootstrap worked fine but when I am doing au run --watch it does not run the server instead it shows me the screen when we normally do just au

image

  • What is the expected behavior?
    After installing any dependency it should run the application

PS: I am new to Aurelia and coming from AngularJS background
Thanks

@monis01 monis01 changed the title aurelia cli does not run after doing npm aurelia cli does not run after installing dependency from npm Feb 15, 2018
@charlesodili
Copy link

I am experiencing the exact same thing with the Contact Manager tutorial application. Everything was working fine until I ran au run --watch after installing bootstrap and jquery, as recommended by the tutorial. While I await a fix for this, I think I will try re-doing the tutorial without the bootstrap and jquery dependencies - whatever they are intended for, in the project, I can write by hand.

@charlesodili
Copy link

charlesodili commented Feb 17, 2018

Update 1

I flipped the installation order and installed jquery before bootstrap. I also just installed jquery instead of specifying jquery@^2.2.4. This got the subsequent au run -watch to not fail.

However, errors in the browser console suggest Aurelia cannot load the bootstrap CSS file from the require statement in app.html. I eventually commented it out, and later replaced it with <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0-alpha.6/css/bootstrap.min.css" integrity="sha384-rwoIResjU2yc3z8GV/NPeZWAv56rSmLldC3R/AZzGRnGxQQKnKkoFVhFQhNUwEyJ" crossorigin="anonymous">.
This was when I eventually got the ERROR [app-router] error that was expected.

@monis01
Copy link
Author

monis01 commented Feb 22, 2018

so, any update on this other than doing tweaks?

@charlesodili
Copy link

See what I explored here: https://twitter.com/chaluwa/status/966611908274130950

@monis01
Copy link
Author

monis01 commented Feb 22, 2018

But the point is tutorial itself is breaking if following official docs (I mean it does not work until if we tweak and trick things out). Btw I have not came across other tutorials for aurelia other than what is mentioned in docs, if anyone here plz do share.
Thanks

@Rud156
Copy link

Rud156 commented Feb 22, 2018

@monis01 I think this will be helpful https://www.youtube.com/channel/UCtWxbsaQzLIHR3Jl-Q0ZlmA

@JeroenVinke
Copy link
Collaborator

for some reason it seems to uninstall aurelia-cli from your node_modules after installing bootstrap, but we'd have to debug it further. I wonder if this has anything to do with the package-lock.json file that NPM creates

@Alexander-Taran
Copy link
Contributor

There is a lot of bad rep for recent versions of npm. Like kining the production servers and such.
I'd wait out the storm

@fkleuver
Copy link
Member

@monis01 @JeroenVinke This is a npm 5.6.0 problem and it should be fixed with the recent 5.7.1. Maybe update the docs to explicitly mention this because lots of people will probably still be running 5.6.0 for a while..

@Alexander-Taran
Copy link
Contributor

CLI has been updated
@monis01 & @charlesodili
do you still have this problem ?

JeroenVinke added a commit to JeroenVinke/cli that referenced this issue Mar 19, 2018
@JeroenVinke
Copy link
Collaborator

I'd think so, because this is an issue with the NPM version installed on your machine, not the version that the CLI uses internally

i've added this to the docs PR here: #747

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

No branches or pull requests

6 participants