-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
fix(tsconfig): support multiple tsconfigs to be specified #327
Conversation
Is this happening because you have multiple tsconfigs? Can you add a test? |
Yeah, I have 3 parallel builds, and each has its own As for adding a test -- any guidance there? |
Specifically, it sounds like your issue is with multiple tsconfig.json files. The bug sounds like it could happen with one Webpack build, irrelevant of parallel. I would just follow the existing tests and add multiple tsconfig files. |
I tried getting a test setup, but am not having any luck even getting the other tests to work -- the webpack4/5 ones work, but after that I get failures:
There are also no docs for setting things up, running builds or tests, so I'm guessing I've set it up wrong (or its my Node version). If you could help set this up it would be greatly appreciated. Thanks! |
GitHub Actions runs the tests and they're passing. Take a look at the setup: |
As I mentioned, I've tried and spent a bunch of time on it and haven't been able to get it working. Also, I'm unsure about how best to observe this change in a unit test, as the only way I could see this is to build something (maybe even the same thing) with different tsconfigs which would result in differing outputs. And to be completely honest, I don't have more time to spend on this issue. Hopefully this can either be merged without a test, or that you or another contributor could create it. |
I was finally able to get a test working with an observable output change. The test fails before my fix and succeeds after it. It also proved that it doesn't have to do with parallel builds just multiple tsconfigs -- which IMO makes this bug even worse. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Thanks for the PR. I removed the caching for a bit. I plan on implementing it in get-tsconfig. |
BREAKING CHANGE: tsconfig passed in by path is now applied regardless of whether it matches |
Preparing the v4 release. Would you mind helping test? npm install -D 'esbuild-kit/esbuild-loader#npm/v4' |
Tried it out and works in my testing! TY |
BREAKING CHANGE: tsconfig passed in by path is now applied regardless of whether it matches
BREAKING CHANGE: tsconfig passed in by path is now applied regardless of whether it matches
Avoids reusing a previous cache if the
tsconfig
prop is differentRefs: #325