Repository navigation
Bundle is now valid / invalid infinite loop #2497
Description
Please provide us with the following information:
OS?
Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows 7
Versions.
Please run
ng --version. If there's nothing outputted, please run in a Terminal:node --versionand paste the result here:
angular-cli: 1.0.0-beta.15
node: 6.7.0
os: win32 x64
Repro steps.
Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
I really didn't do anything special. Issue started in beta.15, and is prelevant af.
The log given by the failure.
Normally this include a stack trace and some more information.
No error, just constantly givesBundle is now valid
then instantly
Bundle is now invalid
Restarting the ng serve works fine, but once I do a change, it starts the loop again.
Mention any other details that might be useful.
Seems to be primarily in IE11, but also happens in chrome.
Thanks! We'll be in touch soon.
Activity
celliott181 commentedon Oct 4, 2016
Does this occur on a freshly installed CLI project?
yusijs commentedon Oct 4, 2016
It's in an existing project, but happened ever since it was new (geberated with cli beta.15)
JtheB commentedon Oct 5, 2016
I have the same loop with a new project. After ng serve it stops at webpack: bundle is now VALID.
ng --version:
angular-cli: 1.0.0-beta.16
node: 6.6.0
os: linux x64
I bascially followed this tutorial: http://stackoverflow.com/documentation/angular2/789/install-angular2/2814/install-angular2-with-angular-cli#t=201608072028333699125
to get to this point.
filipesilva commentedon Oct 9, 2016
What editor are you using? I'm wondering if there's something touching the files on disk, triggering the watchers.
yusijs commentedon Oct 9, 2016
Using the latest version of VS Code. It often follows up with "wait for *.js" (inline, main etc).
I'm questioning if it's some scanner we run at work that messes with it, but it's hard to say. Can probably close this off, as I dont think this is a cli issue anymore.
filipesilva commentedon Oct 10, 2016
Well, there's an undocumented option you can use that might help: #1814. It was put in for a different scenario but maybe helps in yours.
yusijs commentedon Oct 10, 2016
Will def give it a look, thanks!
Den man. 10. okt. 2016, 16:50 skrev Filipe Silva notifications@github.com:
duyhoang commentedon Dec 4, 2016
I have the same problem while having VS Code opened. I close the VS Code and the loop stops.
0cv commentedon Dec 21, 2016
Same like @duyhoang. I checked that "auto save file" is off, I've deactivated all possible extensions, and yet it continues to happen
0cv commentedon Dec 21, 2016
I've put a watcher on the project to check which files are modified. Every 2 minutes, .git/FETCH_HEAD and .git/index.lock are modified. That's probably due to the built-in functionality of VS Code regularly pulling for changes on the Git remote repository. Now the question is why does the angular-cli watches for changes there?
0cv commentedon Dec 21, 2016
OK think I nailed down the issue with VS Code... Looks like the path where tsconfig.json itself is placed is actually watched. In my case, it was put at the root of my project, where .git/ is also located. When I moved tsconfig.json one level down where my Angular2 source code is located, the infinite rebuild loop was solved.
angular-automatic-lock-bot commentedon Sep 6, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.