feat(compiler): v5 browser build - #6852
Merged
Merged
Conversation
…rowser) Exposes transpile/transpileSync/createSystem/scopeCss for in-browser use, built as a separate tsdown entry aliased to browser-safe stand-ins for Node-only deps (fs watcher, chalk, worker threads, on-disk resolve, lightningcss/browserslist). Includes two defensive guards for `ts.sys` being a non-configurable getter on modern typescript builds outside Node.
Contributor
Runtime Benchmark
|
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
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.
What is the current behavior?
GitHub Issue Number: N/A
What is the new behavior?
Add
@stencil/core/compiler/browserentry.Exposes
transpile/transpileSync/createSystem/scopeCss/tsfor in-browser use.Consuming this in a bundler needs Node-builtin polyfills / alias' configured for:
path(actually used)os(actually used)process(actually used)buffer(actually used)fs(no-op)crypto(no-op)util(no-op)url(no-op)Documentation
Does this introduce a breaking change?
Testing
Other information