-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Gulp serve:dist or gulp build doens't work #1982
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
Comments
I tried with the latest version of node, still the same |
@sonic182 do you mean 6.2.1 or 4.4.5? If with 6.2.1, did you also re-install all the npm dependencies? Also what database flavor and version are you using? Not sure that either are relevant to the issue but not sure that it isn't either. Can you also confirm that this issue happens for a completely fresh version of the generator? At first glance I can only tell that it seems related to some combination of the SQL option. Which would also be my best guess as to why it wouldn't have been reported earlier either, at least given that my assumption that the SQL option is less popular holds true and that this is in fact a bug with the generator. |
Sorry, I tried TOO with the last version of node (and with 4.3.0) |
Close this, those files were missing because I haven't sass (In docker containers was the problem and in my machine I updated ruby) |
The problem persist, sorry for close and open |
It happens creating a new proyect and doing gulp dist:serve inmediatly, with mongoose, sequel, nodejs 6, 4, OSX... I've been testing it all day :/ (gulp serve works, but not dist :/) |
FYI |
I did this repo https://github.com/sonic182/sample, It's a generated app with the configs that I want to use, with a Dockerfile and a docker-compose (justo to containerize the app and mongodb) Pretty simple, It doesn't work with node:4, node:6 causes the error adove. (I tried with an Digitalocean vps of docker 14.04 and nothing..) |
Confirm that this is an issue. This problem is present straight away after generating the source. I am also experiencing this on:
On:
Here is one of my stack traces:
Tried switching my node version (via nvm) and rebuilding dependencies on each switch, and the problem persists on all |
Attempting this with a freshly generated app, selecting all the defaults by hitting
|
FYI, no issues when using |
Seems that the culprit might be gulp-angular-templatecache. Here are some related threads: miickel/gulp-angular-templatecache#124 and gulp-community/gulp-header#37 |
Confirm that using the advice in gulp-angular-templatecache will fix this issue. Track miickel/gulp-angular-templatecache#124
and gulp serve:dist will work without error. |
Looks like a possible solution it's as it says here -> miickel/gulp-angular-templatecache#124
but must be added on the generator to avoid this issue with new scaffoldings Ohhh I was testing to post the same answer hahaha @MichaelMarkieta Regards |
error trace ->
[12:33:06] Finished 'copy:server' after 167 ms
[12:33:06] Finished 'copy:extras' after 173 ms
fs.js:839
return binding.lstat(pathModule._makeLong(path));
^
Error: ENOENT: no such file or directory, lstat '/home/sonic182/sandbox/samples/sequel/.tmp/templates.js'
at Error (native)
at Object.fs.lstatSync (fs.js:839:18)
The text was updated successfully, but these errors were encountered: