Closed natemoo-re closed 1 year ago
Latest commit: 58a1df115024788d43a19977768ebdaf43e752e2
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
@natemoo-re the release build seem to have failed. Did we (I) break something by merging https://github.com/natemoo-re/clack/pull/91 or https://github.com/natemoo-re/clack/pull/95?
The latter seems more likely if so. Removing the build
command seems suspicious. Is prepack
not run when/as expected after all?
There were questions around your previous change there so probably related.
// cc @privatenumber
Potentially related and maybe what @natemoo-re followed?
https://github.com/changesets/changesets/issues/837#issuecomment-1222206876
Still don't understand why prepack
is not called, though.
pnpm publish
should trigger it if I understand this correct? https://pnpm.io/cli/publish
and changesets
seem to use it if installed?
Should probably revert in the meantime?
@natemoo-re the release build seem to have failed. Did we (I) break something by merging https://github.com/natemoo-re/clack/pull/91 or https://github.com/natemoo-re/clack/pull/95?
The latter seems more likely if so. Removing the
build
command seems suspicious. Isprepack
not run when/as expected after all?There were questions around your previous change there so probably related.
Ah whoops! I pressed merge and then stepped out. My bad! I'll have to look into what happened here.
I think https://github.com/natemoo-re/clack/commit/a7e6a5a6bcc7e8aa86de29b82f5378fee4b133fe should fix it. I haven't used prepack
before, maybe changesets
doesn't automatically call it...?
@natemoo-re the release build seem to have failed. Did we (I) break something by merging https://github.com/natemoo-re/clack/pull/91 or https://github.com/natemoo-re/clack/pull/95?
The latter seems more likely if so. Removing the
build
command seems suspicious. Isprepack
not run when/as expected after all?There were questions around your previous change there so probably related.
Ah whoops! I pressed merge and then stepped out. My bad! I'll have to look into what happened here.
If anyone should apologize, it's me.
I think https://github.com/natemoo-re/clack/commit/a7e6a5a6bcc7e8aa86de29b82f5378fee4b133fe should fix it. I haven't used
prepack
before, maybechangesets
doesn't automatically call it...?
Right, but prepack
is one of many lifecycle scripts called by the package manager. pnpm
supports them too.
And judging by the code changesets
seems to invoke the underlying package manager.
Let's leave it at this for now. @privatenumber might want to investigate further.
Might be good to add a comment in the code?
If anyone should apologize, it's me.
No worries! Hard to know if CI changes are going to work until they run... This one would have tripped me up as well.
Right, but
prepack
is one of many lifecycle scripts called by the package manager.pnpm
supports them too.
Yeah I would expect this to work! I'm not sure why prepack
wouldn't work, but better safe than sorry I guess?
I'll add a comment!
TIL: https://github.com/pnpm/pnpm/issues/2891
prepack
is not user-defined, though, but I wasn't aware of this difference between npm
and yarn
/pnpm
.
Closes #87.
wrap-ansi
. Kind of a bummer, but it's battle-tested and works very well. Ideally we'll continue exploring our own, smaller version on thefeat/wrap
branch.