You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
esbuild doesn't watch for local library changes while running dev server (cli-cache-enabled=false,preserveSymlinks=true) #25753
library changes are not reflected when using "cli-cache-enabled"=false and "preserveSymlinks"=true and esbuild
when using "@angular-devkit/build-angular:browser" instead of "@angular-devkit/build-angular:browser-esbuild" everything works fine
angular.json
"cli": {
"cache": {
"enabled": false
}
}
"options": {
"preserveSymlinks": true
}
when using "cli-cache-enabled"=true and remove "preserveSymlinks" from otions everything works fine
when using "cli-cache-enabled"=false and remove "preserveSymlinks" application won't start
when using "cli-cache-enabled"=true and "preserveSymlinks"=true changes are not detected
when using "cli-cache-enabled"=true and "preserveSymlinks"=false everything works fine
when using "cli-cache-enabled"=false and "preserveSymlinks"=true changes are not detected
when using "cli-cache-enabled"=false and "preserveSymlinks"=false application won't start
everything works fine = ts and html changes from library work, scss from library doesn't work
I expected to change "@angular-devkit/build-angular:browser" to "@angular-devkit/build-angular:browser-esbuild" and everything would work, but now I will end up in psychiatry because of esbuild
I have the same problem in 17.0.9 regardless of cli cache or preserveSymlinks properties.
Mostly library html and scss changes give me a "No output file changes".
That doesn't seems like everything is working fine:
everything works fine = ts and html changes from library work, scss from library doesn't work
I to am seeing this issue after upgrading to Angular v17.1.0.
My Local Setup:
Mac Ventura v13.3
Angular v17.1.0
Node.js v20.11.0
fwiw, I have spent the last 6 hours trying to find a solution to no avail.
The problem:
Local application serves fine with my local library symlinked in. Library builds fine when I make changes but the browser does not reload with those changes. Investigating in the chrome console Sources tab I see the problem under:
webpack://
node_modules
my-lib
my-file.mjs (is not updated with the changes)
So it seems to be a webpack caching issue.
Any help would be greatly appreciated, thank you.
angular-automatic-lock-bot commented on Feb 20, 2024
Activity
vfg12e9w commentedon Dec 8, 2023
see #26585
see a8dbf1d
tested with angular v17.0.6 and #26585 (comment)
still not working
ChatGPT says: one step closer to madness
problem is probably:
alan-agius4 commentedon Dec 8, 2023
Hi @vfg12e9w, I am unable to replicate this, kindly provide a minimal reproduction.
alan-agius4 commentedon Dec 9, 2023
@3z6tfx6d, from the repro steps, it doesn’t look like your configuring the typescript path mappings are described in #26585 (comment)
xx11sw3om commentedon Dec 9, 2023
repeat the steps and you will see that it does not work regardless of whether you write the typescript path mappings (#26585 (comment)) or not
I'm crazy, but I'm not that crazy
therefore it is questionable whether #26585 is actually fixed or not, because the steps are more or less the same
1 remaining item
fix(@angular-devkit/build-angular): handle updates of an `npm link` l…
fix(@angular-devkit/build-angular): handle updates of an `npm link` l…
e23gap32oq commentedon Dec 14, 2023
I can confirm that in version 17.0.7 it works with cli-cache-enabled=false and preserveSymlinks=true
achrysanthakopoulou commentedon Jan 10, 2024
I have the same problem in 17.0.9 regardless of cli cache or preserveSymlinks properties.
Mostly library html and scss changes give me a "No output file changes".
That doesn't seems like everything is working fine:
jyounce-aim commentedon Jan 20, 2024
Hi everyone,
I to am seeing this issue after upgrading to Angular v17.1.0.
My Local Setup:
Mac Ventura v13.3
Angular v17.1.0
Node.js v20.11.0
fwiw, I have spent the last 6 hours trying to find a solution to no avail.
The problem:
Local application serves fine with my local library symlinked in. Library builds fine when I make changes but the browser does not reload with those changes. Investigating in the chrome console Sources tab I see the problem under:
webpack://
node_modules
my-lib
my-file.mjs (is not updated with the changes)
So it seems to be a webpack caching issue.
Any help would be greatly appreciated, thank you.
angular-automatic-lock-bot commentedon Feb 20, 2024
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.