fix: set same marko linked config in all compiler options #155
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.
Using output specific compiler config in a transform is not supported since the transform stage is cached across outputs. The
renderAssetsTransform
here was using an internal compiler config option that was only set in the ssr compiler which would lead to issues if the browser code was compiled first.This PR updates that config option to be set on all of the compiler configs so that the option is there regardless and is cached correctly.
Resolves marko-js/marko#2336