Conversation
🦋 Changeset detectedLatest commit: 3188ff7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 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. |
This way the files are identical and git has the best chance possible to retain history.
We're keeping the tests, for now at least. This ensures that we did everything right, and @labs/task continues to function the same as it did before.
7b61d89 to
948ac3b
Compare
Doing this results in multiple wireit invocations, which causes wasted effort in handling caches, as well as unclear output.
packages/tests/package.json
Outdated
| } | ||
| }, | ||
| "test:common:prod": { | ||
| "command": "MODE=prod node ./run-web-tests.js", |
There was a problem hiding this comment.
Nit, but can MODE=prod be removed because it's also passed in "env"?
| ] | ||
| }, | ||
| "test:dev": { | ||
| "command": "MODE=dev node ../tests/run-web-tests.js \"development/**/*_test.js\" --config ../tests/web-test-runner.config.js", |
There was a problem hiding this comment.
Nit: MODE=dev and MODE=prod (in the next test) could be moved into wireit env, but non blocking.
| "name": "ssr", | ||
| "path": "packages/labs/ssr" | ||
| }, | ||
| { |
There was a problem hiding this comment.
VS Code has gotten a lot better about working with nested packages that aren't workspace roots, so I don't know if we need to add every package here anymore. I'm also fine with it.
There was a problem hiding this comment.
+1, but not in this PR
packages/labs/task/README.md
Outdated
| A controller for Lit that renders asynchronous tasks. | ||
|
|
||
| ## Overview | ||
| This package has graduated from labs! It is now available as `@lit/task`. This package will no longer be updated, but it will continue to work and get updates through the ^1.0.0 version range of `@lit/task` because it's now just a re-export of that package. This should reduce duplication of code while everyone migrates their imports and dependencies. |
There was a problem hiding this comment.
I think the "it's now just a re-export of that package" part should com earlier, then mention this package is a proxy and won't be updated.
We might want a headline here too.
| @@ -0,0 +1,165 @@ | |||
| { | |||
| "name": "@lit/task", | |||
| "version": "0.1.0", | |||
There was a problem hiding this comment.
This could be 0.0.0 to make it clear it hasn't been released yet.
| export default litProdConfig({ | ||
| packageName: createRequire(import.meta.url)('./package.json').name, | ||
| entryPoints: ['deep-equals', 'index', 'task'], | ||
| external: ['@lit/reactive-element'], |
There was a problem hiding this comment.
In the future I think we should change all of these to external: (id) => !(id.startsWith('.') || id.startsWith('/')),
No description provided.