fix: update default swc config to be compatible with @swc/cli@^0.3.0 #2490
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.
Reopening #2481 after branch changes.
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?
As of
@swc/cli@0.3.0
, output paths no longer follow the same behavior as is configured in tsconfig. As of 0.3.5, however, astripLeadingPaths
option was introduced to revert back to this functionality.See #2467 (comment) for more context.
Issue Number: N/A
What is the new behavior?
Default swc configuration now includes the
stripLeadingPaths
option.Does this PR introduce a breaking change?
Other information
I manually tested older versions of
@swc/cli
with this option and they still worked without issue. I also validated that setting this with@swc/cli@0.3.5
resolves the issue, outputting to the expected destination.