docs(custom-webpack): document ts-node configuration for custom tsconfig (fixes #1162)#2206
Open
just-jeb wants to merge 2 commits into
Open
docs(custom-webpack): document ts-node configuration for custom tsconfig (fixes #1162)#2206just-jeb wants to merge 2 commits into
just-jeb wants to merge 2 commits into
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
just-jeb
force-pushed
the
fix/1162-document-ts-node-config
branch
from
093209f to
d144e86
Compare
The previous example used `module: 'commonjs'` which the builder hard-overrides in its programmatic ts-node compilerOptions, so the example would have appeared to work for the wrong reason. Switch to `target` and `paths` (genuinely honored), and add a note about ts-node registering once per builder run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
No documentation explaining how to configure ts-node behavior (e.g. module resolution, custom tsconfig) for custom webpack config files and index transform files.
Issue Number: #1162
What is the new behavior?
The custom-webpack README includes a section explaining that ts-node configuration can be provided via the
ts-nodesection intsconfig.json, with examples for both inlinecompilerOptionsoverrides and pointing to a separate tsconfig file viats-node.tsconfig.Does this PR introduce a breaking change?
Other information
This is a docs-only change. The feature was already working — users just lacked documentation on how to configure it.