-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
DataViews build-wp: don't bundle the date package #67612
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: 0 B Total Size: 1.83 MB ℹ️ View Unchanged
|
Co-authored-by: jsnajdr <jsnajdr@git.wordpress.org> Co-authored-by: youknowriad <youknowriad@git.wordpress.org>
Followup to #67590: let's unbundle also the
@wordpress/date
package because internally it has a "settings" object that is also a singleton. These global settings are initialized by thewp-date-js-after
inline script:However, if
@wordpress/date
is bundled, it doesn't see these initialized settings. AndgetSettings().timezone
is the only thing that thedataviews/wp
bundle uses: in theDateTimePicker
component fromcomponents
.How to test:
Build the
dataviews/wp
bundle and verify that the new build doesn't bundledate
modules. They can be identified by the comment that every bundled module starts with:These bundled modules should be replaced with