Open bagbag opened 1 year ago
Sorry for delay, sounds like symlinks are disabled in ng
/cc @alan-agius4
You can try to enable "preserveSymlinks": true
in the build
section of your angular.json
?
It is and was enabled, as I use shared types between client and server. So this does not fix the problem.
@bagbag Can you try to reproduce it with pure webpack setup
As I have no experience with webpack, I simply tried it with https://levelup.gitconnected.com/setup-tailwind-css-with-webpack-3458be3eb547, created a symlink to that css file, imported it in the .js file, and... it worked.
@bagbag That is why I think something wrong in angluar, postcss-loader don't know about symlinks nothing
/cc @alan-agius4
@bagbag Hope you solved your problem, if no please open an issue in angular-cli repo (you can ping me), postcss-loader doesn't know nothing about files/symlinks and etc, so the problem is not here
If you still have a problem can you provide a reproducible example?
@alexander-akait I haven't tested it with the current versions, but there was nothing solved back then. There is already an issue and example at https://github.com/angular/angular-cli/issues/24705.
Preamble
Yes, this bug report is very unspecific to webpack and I cannot say what is wrong where, because I don't have the knowledge, but the tailwind developer said the bug could be in webpack and the angular developer said the problem seems to rely in webpack.
My previous issues leading me to webpack: https://github.com/tailwindlabs/tailwindcss/issues/10555 https://github.com/angular/angular-cli/issues/24705
Information from @thecrypticace (tailwind developer)
He said that he is willing to provide additional information if needed.
Information from @alan-agius4 (angular developer)
Bug report
New tailwind classes are not added in ng serve without restarting it, while a symlink exists in tailwinds content path. This issue can be fixed by removing the symlink. Now class changes are added without restarting ng serve. It does not matter what file type it is, the existence of a symlink is enough to break it.
Actual Behavior
Changes in files are not reflected in watched output.
Expected Behavior
The dependency should be invalidated and recompiled.
How Do We Reproduce?
setup new angular project:
replace html in app.component.ts with following:
start:
You will see a red square. Now change
bg-red-500
tobg-green-500
-> the square will disappear, as the new tailwind class is not generated. A restart ofng serve
will add it.If you remove the symlink at
src/assets/README.md
and restartng serve
, the problem above does not appear.