-
Notifications
You must be signed in to change notification settings - Fork 96
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
feat(tools): add pfe cli #2336
base: main
Are you sure you want to change the base?
feat(tools): add pfe cli #2336
Conversation
🦋 Changeset detectedLatest commit: 92373b8 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 |
✅ Deploy Preview for patternfly-elements ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
c7dc9c8
to
0eac0ab
Compare
this reduced the number of errors when running the lit-labs/analyzer from 59 to 40
this commit bring the number of errors down from 50 to 17
I'm pretty happy with how the analyzer works so far. It could use some TUI polish, and is still missing the demos, but once the next version of lit analyzer releases we'll be in range |
prevents compile-time overload with incompatible nodeJS globals
shuffle files around use package imports fix some typescript errors
fixes some esoteric analyzer bugs
What I did
pfe
cligenerate|new
: same as create-elementanalyze
: generate custom-elements.json@lit-labs/react
or some such (npm)