You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Modify the lwc compiler to avoid using the project wide babel.config.js file. This was discovered when adding support to LWC LSP when opening standalone projects. If that standalone project was using a babel.config.js file, it was interfering with the lwc compiler babel transforms, which should be isolated. lwc compiler already pases babelrc: false as a default option. babelConfig: false is the way to disable the project wide config. Project wide configs are new in babel 7.x.
Does this PR introduce a breaking change?
Yes
No
If yes, please describe the impact and migration path for existing applications:
Please check if your PR fulfills the following requirements:
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.
Details
Modify the lwc compiler to avoid using the project wide babel.config.js file. This was discovered when adding support to LWC LSP when opening standalone projects. If that standalone project was using a babel.config.js file, it was interfering with the lwc compiler babel transforms, which should be isolated. lwc compiler already pases babelrc: false as a default option. babelConfig: false is the way to disable the project wide config. Project wide configs are new in babel 7.x.
Does this PR introduce a breaking change?
If yes, please describe the impact and migration path for existing applications:
Please check if your PR fulfills the following requirements: