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

wiredep doesn't get bower files injected after app is generated for first time #1710

Closed
deepu105 opened this issue Jul 11, 2015 · 23 comments
Closed
Milestone

Comments

@deepu105
Copy link
Member

Isnt this suppose to be triggered after app generation, doesnt seems to work atleast in windows.

Need to take a closer look

@jdubois
Copy link
Member

jdubois commented Jul 11, 2015

That would be a big issue, yes please post updates on your findings!

@deepu105
Copy link
Member Author

can someone confirm if this works in linux/mac ?

@gmarziou
Copy link
Contributor

Works on linux ubuntu with both gulp and grunt

@deepu105
Copy link
Member Author

@gmarziou then this might be another windows only issue :(

@deepu105
Copy link
Member Author

this is weird it seems to be working now. I can vouch that it didnt work last few times i tried.

@atomfrede
Copy link
Member

@deepu105 When I was testing my windows machine (the gradle gatling stuff) I've seen it too (I think). After generating the app, all bower files where missing from index.html. After doing grunt serve everything was fine, but I didn't dig any deeper.

@gmarziou
Copy link
Contributor

There are often beginners (not your case of course) who post issues about seeing only footer, most of the times they did not follow the doc or had an error duirng installation that they did not notice.

We could avoid these issues if the index.html contained a help section that would show only if angular app did not successfully intialize.

That would be a smoke test and in case of error there could be a link to a section of the online documentation.

@atomfrede
Copy link
Member

@gmarziou Sounds like a reasonable idea. Will check if I can reproduce it on windows next week (as you said it works on linux, same for me here)

@jdubois
Copy link
Member

jdubois commented Jul 12, 2015

@deepu105 @atomfrede @gmarziou you can have Windows 10 preview for free on a VirtualBox machine, and the rumors is that it will stay free after the preview...

@deepu105
Copy link
Member Author

Since i had windows 8 im getting 10 for free on 29th july anyways

@gmarziou
Copy link
Contributor

So finally Armageddon is for July 29th ;)

@deepu105
Copy link
Member Author

Im reopening this issue, coz this seems to be appearing on and off, I still dont know how to reproduce, but randomly this happens.
May be this is only in windows but given the unstable nature i doubt. This is a very bad thing for new comers and should be fixed

@deepu105 deepu105 reopened this Jul 21, 2015
@deepu105
Copy link
Member Author

I guess a sure shot way is to bind the these two tasks into the mavan or gradle build so that it is not missed

@andidev
Copy link
Member

andidev commented Jul 21, 2015

Grunt build is run from at least maven and it should inject the files.

@atomfrede
Copy link
Member

I've created two projects just now on windows 8 (one with maven, one with gradle) and both times wiredep injected all files.

@deepu105
Copy link
Member Author

@atomfrede for me its working on and off and i dont know whats causing this behavior im on windows 8 as well. had an embarrassing moment coz of this when i was doing the JH demo to Singapore spring user group earlier

@atomfrede
Copy link
Member

anybody able to reproduce it?

@jdubois
Copy link
Member

jdubois commented Aug 18, 2015

it looks like nobody is able to reproduce this, so I'm closing it.

@jdubois jdubois closed this as completed Aug 18, 2015
@jdubois jdubois modified the milestone: 2.20.0 Aug 21, 2015
@mallim
Copy link

mallim commented Sep 11, 2015

if somebody got the same error in windows and google to this page like me, I got it solve by first performing:

Then perform the installation steps:

  • npm install -g yo
  • npm install -g bower
  • npm install -g generator-jhipster

and the wiredep works again for:

  • yo jhipster

@deepu105
Copy link
Member Author

Thats interesting
On 11 Sep 2015 09:17, "Ian Lim" notifications@github.com wrote:

if somebody got the same error in windows and google to this page like me,
I got it solve by first performing:

Then perform the installation steps:

  • npm install -g yo
  • npm install -g bower
  • npm install -g generator-jhipster

and the wiredep works again for:

  • yo jhipster


Reply to this email directly or view it on GitHub
#1710 (comment)
.

@gmarziou
Copy link
Contributor

@mallim Your instructions should mention that it's Python 2.7.x that you must install not Python 3.x

@mallim
Copy link

mallim commented Sep 11, 2015

@gmarziou In fact, I installed Python 3.X, my environment as follows:

  • Windows 8.1
  • npm 2.11.3
  • node 0.12.7

@gmarziou
Copy link
Contributor

Well I think you should re-consider it, I recently had to downgrade Python on a co-worker's PC for the reason below:

There's a well known and very old gyp issue and as a consequence node-gyp does not support Python 3 either, even NodeJS requires gyp to build.

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