-
-
Notifications
You must be signed in to change notification settings - Fork 246
preserveSymlinks option not honored #332
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
Thanks for the detailed report. I'm afraid I'm not able to look at this myself right now. This is definitely functionality we would want. If you'd like to take a look we're happy to look at PRs and collaborate! |
I think this problem is coming from chokidar, paulmillr/chokidar#696. |
I was trying to create a branch for this fix but I am not able to publish my branch due to access to this repo. Could you please provide me the access? |
Hi @gyancse08, Thanks for looking into this! Please could you fork the fork-ts-checker-webpack-plugin repo, work on that and send a pull that way? |
When I publish my branch I am getting this error: only change is following, I will appreciate if someone else fixes the same.
|
You need to fork this project, push the changes to a branch on your fork and then send a pull request, that's the "github workflow". :) |
@ryedin |
@piotr-oles Hi, the v5.0.0@beta fixed the problem for me within my npm@7 workspace project. However, the v6 master branch detects a change, but it continues to compile with the previous file contents of the symlinked file, not the new contents. Have these commits been merged into the latest master? |
Current behavior
If you have folders of code that are symlinked into src (very common pattern for monorepo style development), the type checker does not re-trigger when those files are changed.
Expected behavior
I should be able to make changes to those symlinked files and have the typechecker correctly re-run checks.
Steps to reproduce the issue
Setup a basic CRA app with typescript enabled. Have another folder of typescript code sitting as sibling to your project. Create a symlink within the CRA
src
folder to your "shared" folder.add
"preserveSymlinks": true,
to yourtsconfig.json
.If you create a typescript error on purpose in the shared code and start the app you will observe the checker does correctly pick up the code and display the error. However, if you fix the error, the checker does not automatically re-check as it would if the file lived natively in the CRA app's
src
dir.Environment
The text was updated successfully, but these errors were encountered: