-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(serializer): replace LWC scope tokens (BREAKING CHANGE) #185
Conversation
"@lwc/compiler": "^2.48.0", | ||
"@lwc/engine-dom": "^2.48.0", | ||
"@lwc/engine-server": "^2.48.0", | ||
"@lwc/synthetic-shadow": "^2.48.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lwc/compiler
v2.48.0 added the cssScopeTokens
return value, which we need. We might as well bump every other LWC peer dep as well, since folks shouldn't be mixing-and-matching different versions of LWC packages.
4e3a7c0
to
ff3597f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good--just one question about whether you considered using the existing format of [lwc:scope-token]
?
I like it! Let's do |
This reverts commit b80a978.
On second thought, how about |
I don't have a strong opinion but I'm leaning towards the previous version because it's self-descriptive. |
This reverts commit 7482ddc.
Sounds good, let's stick with the first one then! |
New version of #184
In serialized HTML, all scope tokens are replaced with
__lwc_scope_token__
. This is a breaking change because it breaks all existing snapshots, and because we now require the LWCpeerDependency
of 2.48+.