feat(CLI): Added possibility to have custom config location for swc #870
Conversation
This file contains 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
|
|
desout
force-pushed
the
config-file-swc
branch
from
d8d5f00 to
e541fe6
Compare
desout
changed the title
|
@Brooooooklyn Could you take a look at this little feat? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We encountered an issue that requires us to specify a custom SWC configuration file when using the
swc-node/registerpackage. Our project does not use TypeScript, and we wish to avoid placing irrelevant files liketsconfig.jsonin our root directory. Additionally, we are integrating Jest with@swc/jest, which leads to conflicts with the root.swcrcfile.To resolve this, we need the ability to specify a custom path for the
.swcrcfile and prevent the root.swcrcfrom being used during real-time node building. The SWC API allows for this through theconfigFileproperty, which can be implemented similarly to settingSWCRC=true.Our migration process is currently hindered by this limitation, and we've had to temporarily override your package locally.