-
Notifications
You must be signed in to change notification settings - Fork 400
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(engine-dom): support LWC v5 compiler slot format #3973
Conversation
😞 |
@@ -5,155 +5,164 @@ import Component from 'x/component'; | |||
import ComponentWithProp from 'x/componentWithProp'; | |||
import ComponentWithTemplateAndStylesheet from 'x/componentWithTemplateAndStylesheet'; | |||
|
|||
describe('compiler version mismatch', () => { |
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.
Github UI totally mangled this file's diffs 😞
const { rollup } = require('rollup'); | ||
const lwcRollupPlugin = require('@lwc/rollup-plugin'); |
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.
sanity check: are none of the slot-related tests in @lwc/integration-tests
affected by this slot format change? That project's build.js has its own separate entry point.
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.
It's possible that @lwc/integration-tests
is affected, but I'm hoping the Karma tests are sufficient. The @lwc/integration-tests
are not terribly well-maintained at this point.
Details
In #3883 we changed the format of the compiled components to use the
slotAssignment
key rather thanattrs.slot
.Unfortunately this breaks anyone who uses the LWC v5 compiler in combination with the v6 engine.
Version mismatches between the compiler and the engine have never been supported, but as a temporary measure, this PR proposes that we support v5-compiler-plus-v6-engine.
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item
W-14974789