We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is follow-up work for custom element registry pivots (#2724).
The scoped registry polyfill we've implemented does not need to be an LWC-only internal detail. It could be exposed as a general-use package.
In particular, this would allow Locker to hook into it to avoid duplication of effort.
The text was updated successfully, but these errors were encountered:
This issue has been linked to a new work item: W-11884700
Sorry, something went wrong.
feat: extract pivots into @lwc/scoped-registry package
2bc3636
Fixes #3096
Pivots were dropped in #3310
Successfully merging a pull request may close this issue.
This is follow-up work for custom element registry pivots (#2724).
The scoped registry polyfill we've implemented does not need to be an LWC-only internal detail. It could be exposed as a general-use package.
In particular, this would allow Locker to hook into it to avoid duplication of effort.
The text was updated successfully, but these errors were encountered: