Conversation
🦋 Changeset detectedLatest commit: 3a7d6cd The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
📊 Tachometer Benchmark ResultsSummarynop-update
render
update
update-reflect
Resultsthis-change
render
update
update-reflect
this-change, tip-of-tree, previous-release
render
update
nop-update
this-change, tip-of-tree, previous-release
render
update
this-change, tip-of-tree, previous-release
render
update
update-reflect
|
|
The size of lit-html.js and lit-core.min.js are as expected. |
|
Interesting - this adds 231 to lit-core.min.js. I think we'll still want to update dependencies, but understand what's going on here. Maybe |
|
Manual inspection of the bundle shows the difference in bytes are due to some variable names being minified to 2 chars instead of 1. It seems to be variation from the change in the version of the The failing tests were due to the I also updated the rollup and related packages for the localize examples and starter kits. |
| @@ -0,0 +1,2 @@ | |||
| --- | |||
| --- | |||
There was a problem hiding this comment.
@augustjk I suppose we should include the starter kits here, since updating dev dependencies is more relevant than for our own packages.
I so wonder if we should mention the rollup and terser updates for our packages as well though, since conceivably they could effect people if something goes wrong. wdyt?
justinfagnani
left a comment
There was a problem hiding this comment.
Your changes LGTM @augustjk. Thanks!
* Fixes #4655 -- Move localize setup to resolve import loop Localize has an import loop, because submodules are importing from their root. To resolve this `msg`, `installed` and `_installMsgImplementation` have moved to a new submodule. Imports to `msg` stay intact, through an explicit export.
abef13d to
3a7d6cd
Compare
Updating Rollup and related packages, initially to try to get rid of this error message we have on npm install:
npm install error
It turns out that rollup-plugin-sourcemaps is seemingly unmaintained right now and has this issue open for Rollup 3 and 4 compatibility. A user reported that an npm override for
@rollup/pluginutilsfixed the error though, so I applied that as well.