-
Notifications
You must be signed in to change notification settings - Fork 926
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
Monorepo playground #4732
Monorepo playground #4732
Conversation
📊 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. |
a7789e0
to
e70ed0d
Compare
🦋 Changeset detectedLatest commit: f03fbcc The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types 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 |
e70ed0d
to
56a30c1
Compare
56a30c1
to
e7f034d
Compare
@@ -0,0 +1,11 @@ | |||
{ | |||
"source": "https://lit.dev/playground/#gist=aece301df423847e72b1a85e1e9caf75", |
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.
Is this intended to be committed? If so, it seems weird to name it by issue.
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.
Yes. In working on Virtualizer issues, I've found that committing a minimal repro, followed by the fix, makes for a very convenient PR review process. A reviewer can check out the PR branch, temporarily detach HEAD to view the repro without the fix, then switch back to the tip of the branch to review the fix.
I've also found through experience that when a repro case is part of a workflow like this, it's easiest to use the issue number as the name of the repro, to minimize cognitive load.
@@ -0,0 +1 @@ | |||
{} |
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.
Is it possible to include defaults here that make the example installable standalone?
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.
The Lit libraries are intentionally left out of the package.json
so that examples will automatically default to using the versions from the current branch of the monorepo.
I wasn't thinking of standalone examples as a P0/P1 use case, but if we want to support that, I think the best way of doing it would be to add an export:standalone
script that adds deps into the exported package.json
.
.gitignore
Outdated
@@ -7,4 +7,4 @@ node_modules/ | |||
/temp | |||
.idea | |||
/scripts/check-size-out.md | |||
|
|||
/playground/p/**/package-lock.json |
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.
Can we add a folder here for playgrounds to be auto-ignored and call it out in the readme?
e.g. /playground/scratch/**
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.
Sure, that's a good idea!
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.
Added!
e7f034d
to
558f837
Compare
eef6aa5
to
f3c470f
Compare
f3c470f
to
f03fbcc
Compare
Edit: Ready for approval
Per discussions in the review here and in the last Lit Eng meeting, I've removed the commits for the illustrative playground examples and am taking this PR out of Draft status—it's now ready for approval.
As discussed in a recent Lit Eng meeting, here's a draft PR exploring what it might look like to add a playground to the Lit monorepo.
See playground/README.md for rationale and details.
Making this a draft primarily because I included a couple of additional commits, adding specific playground examples for the purpose of illustration; for cleanliness, we'd probably want to remove those before landing this PR.