Skip to content
This repository has been archived by the owner on Jul 8, 2020. It is now read-only.

unexpected behaviour: gulp watch and gulp build at the same time #227

Closed
gruppjo opened this issue Aug 10, 2015 · 8 comments
Closed

unexpected behaviour: gulp watch and gulp build at the same time #227

gruppjo opened this issue Aug 10, 2015 · 8 comments
Milestone

Comments

@gruppjo
Copy link
Contributor

gruppjo commented Aug 10, 2015

Sometimes when running gulp watch and gulp build at the same time the app/main/constants/config-const.js is emptied.

@gruppjo gruppjo added this to the 1.3.0 milestone Aug 10, 2015
@RomainGoncalves
Copy link

Ahhh is that why?! I was wondering why my const file was empty when I was running gulp build!
And then no matter if you try to run either command alone, the file stays empty...

@MathiasTim
Copy link
Contributor

yeah, thats why. Unfortunately we cannot reproduce this issue continuously. Can you? Thanks for your help!

@gruppjo gruppjo removed this from the 1.3.0 milestone Sep 2, 2015
@gruppjo
Copy link
Contributor Author

gruppjo commented Nov 9, 2015

today I encountered these errors in addition to config-const.js being emptied:

[18:13:05] 'clean' errored after 1.76 s
[18:13:05] Error: ENOTEMPTY: directory not empty, rmdir '/Users/jonathan/Projects/m-way/qr-code-test/.tmp/main/styles'
    at Error (native)

I suspect this is because build is trying to empty a directory watch is still working on.

[18:07:28] 'build-templates' errored after 1.87 s
[18:07:28] Error: EEXIST: file already exists, mkdir '/Users/jonathan/Projects/m-way/qr-code-test/www/main/templates'
    at Error (native)
[17:25:30] 'build-assets' errored after 283 ms
[17:25:30] Error: ENOENT: no such file or directory, stat '/Users/jonathan/Projects/m-way/qr-code-test/www/main/assets/images'
    at Error (native)
[17:25:30] 'build-templates' errored after 1.5 s
[17:25:30] Error: ENOENT: no such file or directory, stat '/Users/jonathan/Projects/m-way/qr-code-test/www/main/templates/list.html'
    at Error (native)
[17:25:18] 'build-assets' errored after 499 ms
[17:25:18] Error: ENOENT: no such file or directory, stat '/Users/jonathan/Projects/m-way/qr-code-test/www/main/assets/fonts/ionicons.ttf'
    at Error (native)

No Idea why these might occur. But I suspect the same origin as the first one. Working on the same files concurrently.

They're quite reproducible with the following setup

$ node -v
v4.2.1
$ npm -v
2.14.7

Maybe I can do some more research if others have this problem as well under new node versions and gulp running concurrent tasks in different processes.

@MathiasTim
Copy link
Contributor

+1 having this issue from time to time.

@gauravarora
Copy link

I have this problem too with the following versions

bash-3.2$ node -v
v4.2.1
bash-3.2$ npm -v
3.3.12

@gianko
Copy link

gianko commented Apr 20, 2016

+1

Is there a way to "refill" the file?

Now I'm getting Uncaught Error: [$injector:unpr] Unknown provider: ConfigProvider <- Config ...

@gruppjo
Copy link
Contributor Author

gruppjo commented Apr 21, 2016

We usually just use git and simply checkout the file.
git checkout app/main/constants/config-const.js

you can generate a new file with the sub-generator:
yo m-ionic:constant config --template=config

@gruppjo
Copy link
Contributor Author

gruppjo commented Feb 17, 2017

Closing this one. Discussion moved the new collective ticket: #453

@gruppjo gruppjo closed this as completed Feb 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants