| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
🦋 Changeset detectedLatest commit: 7c81b29 The changes in this PR will be included in the next version bump. 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 💥 An error occurred when fetching the changed packages and changesets in this PRSome errors occurred when validating the changesets config: The package "@changesets/apply-release-plan" depends on the ignored package "@changesets/test-utils", but "@changesets/apply-release-plan" is not being ignored. Please add "@changesets/apply-release-plan" to the `ignore` option. The package "@changesets/cli" depends on the ignored package "@changesets/test-utils", but "@changesets/cli" is not being ignored. Please add "@changesets/cli" to the `ignore` option. The package "@changesets/config" depends on the ignored package "@changesets/test-utils", but "@changesets/config" is not being ignored. Please add "@changesets/config" to the `ignore` option. The package "@changesets/get-dependents-graph" depends on the ignored package "@changesets/test-utils", but "@changesets/get-dependents-graph" is not being ignored. Please add "@changesets/get-dependents-graph" to the `ignore` option. The package "@changesets/git" depends on the ignored package "@changesets/test-utils", but "@changesets/git" is not being ignored. Please add "@changesets/git" to the `ignore` option. The package "@changesets/pre" depends on the ignored package "@changesets/test-utils", but "@changesets/pre" is not being ignored. Please add "@changesets/pre" to the `ignore` option. The package "@changesets/read" depends on the ignored package "@changesets/test-utils", but "@changesets/read" is not being ignored. Please add "@changesets/read" to the `ignore` option. The package "@changesets/release-utils" depends on the ignored package "@changesets/test-utils", but "@changesets/release-utils" is not being ignored. Please add "@changesets/release-utils" to the `ignore` option. The package "@changesets/should-skip-package" depends on the ignored package "@changesets/test-utils", but "@changesets/should-skip-package" is not being ignored. Please add "@changesets/should-skip-package" to the `ignore` option. The package "@changesets/write" depends on the ignored package "@changesets/test-utils", but "@changesets/write" is not being ignored. Please add "@changesets/write" to the `ignore` option. |
Sorry, something went wrong.
|
It would be great to include some before/after screenshots in the PR summary + call out behavior differences (if there are any) |
Sorry, something went wrong.
Sorry, something went wrong.
yep, will add more info when theres more progress but for now i have one recording and will add more later |
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 60.45455% with 87 lines in your changes missing coverage. Please review. @@ Coverage Diff @@
## next #1879 +/- ##
==========================================
+ Coverage 79.64% 81.09% +1.44%
==========================================
Files 52 53 +1
Lines 2412 2348 -64
Branches 710 714 +4
==========================================
- Hits 1921 1904 -17
+ Misses 441 402 -39
+ Partials 50 42 -8 ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
Do we still need to handle v1 configs in v3 or should we just remove that code? |
Sorry, something went wrong.
|
iI think it's safe to remove any mentions of v1 configs from the codebase |
Sorry, something went wrong.
There was a problem hiding this comment.
i'm thinking that the log silencers for the tests should probably always be on and the functions removed, but that would be a ton of changes so i left them as-is in this PR
Sorry, something went wrong.
|
@beeequeue could you sync this with next? |
Sorry, something went wrong.
|
i added a section in the pr body for the current follow-ups that will be needed if we don't do them in this pr |
Sorry, something went wrong.
|
One extra thing we should do before landing this is to check out how the "delegated auth mode" renders now. It's when we spawn npm so it can handle OTP-related prompting. Would you be able to test that out? |
Sorry, something went wrong.
|
im not sure how to trigger it, but when i tried to publish a package and it failed i got a very weird looking output: screenshot
after i logged in and tried again it worked and looks a bit weird but okay-ish screenshot
i think this is because i added the spinner after i migrated the npm publishing files, and didn't check how it affected them. i would love if we could use tasks for it but it would require larger refactoring of the publishing functions which is why i dropped that idea |
Sorry, something went wrong.
|
Hm, that's weird that both runs ended up being indented differently... 🤔 As an experiment, I also wanted to take a look how this would look like completely without the "guide". For that, I had to open a PR here: bombshell-dev/clack#500 I think it's worth waiting a couple of days for that PR to possibly get merged in so we could test both versions in the repo here |
Sorry, something went wrong.
|
presumably the different indentation is from the npm command's output being logged without going through clack's formatting, unlike in the error one where they are handled and printed with them |
Sorry, something went wrong.
|
Overall, this looks great. The only thing I'd like to do now is to properly compare the withGuide: true/false variants to decide which one feels better. I'll try to find the time to do that this week. |
Sorry, something went wrong.
|
imo the publish command needs to be redone, but i would also be okay with leaving it as-is for another pr |
Sorry, something went wrong.
|
What kind of a makeover do u think about? |
Sorry, something went wrong.
There was a problem hiding this comment.
Since this merges to next, we'd need to manually close the issue after merge.
Sorry, something went wrong.
|
we can add them manually via the Development section to the right, but for some reason github can't find #1043 in the dropdown 💤 |
Sorry, something went wrong.
|
i'm gonna do a final check that each command still looks okay after all the rebasing, then i'll merge it. |
Sorry, something went wrong.
|
Maybe I'm misremembering, but I think the auto-close only works when merging to the default branch. So next wouldn't work. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
closes #1814
closes #1043
closes #1861
closes #1814
part of #1869
replaces enquirer with the slightly smaller and more modern @clack/prompts, whose API is also a lot nicer in my opinion
it also replaces @inquirer/external-editor with launch-editor, which is quite a lot smaller, works better in my experience, and is more flexible allowing us to remove the hack in packages/cli/src/commands/add/index.ts
things to do in follow-up PRs
recordings / screenshots
Recordingscancelling at any point: https://asciinema.org/a/HxMUViS932Pwi5Oj
changeset add: https://asciinema.org/a/1JFbvyuuVbbfOjuy
changeset init with existing config:

changeset version with pre-release:

changeset tag: https://asciinema.org/a/aVKLczi02OzZWHrk
changeset status --verbose:

changeset publish:
non-interactive (otp, oidc): https://asciinema.org/a/7tjKcMe3d1NNshUc
interactive (passkey): https://asciinema.org/a/yF9PEOwG2sROT5Zz
changes to messages/texts
changesgeneral rules i tried to follow
texts
legend:
add
${error.toString()}