Closed with-heart closed 2 months ago
Latest commit: 6e9f284c7c1b7fb78e4a3b5bd994a2bd0b6528a8
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
changed devDependencies.xstate versions to workspace:^
don't do this if not needed - this might interfere with how Changesets are set up right now, you'd have to rework publishing scripts to enable this
don't do this if not needed - this might interfere with how Changesets are set up right now, you'd have to rework publishing scripts to enable this
Oof. Okay I'll see what I can do
@Andarist do you mean scripts/bump-peer-dep-ranges.js
or something else? I'm not sure where devDependencies
using workspace:
would affect things
changeset publish
might have issues with workspace ranges. Although perhaps they don’t affect pnpm repos - that would have to be tested. It definitely doesnt work with Yarn Berry
I'll set up a repo and test it later just to see what happens
I resolved the typecheck
errors for all of the packages except @xstate/vue
. I don't know Vue so gonna need some help with that bit
I fixed the Vue issue. I think something weird is happening with Vue types - their shallowRef
function introduces some weirdness with deferred conditional types. I prepared a slimmed-down xstate-less repro of the problem: TS playground
@Andarist I found references to the workflow:
protocol in changesets/changesets
in both CHANGELOG.md
files and the codebase.
I also created a test project locally and verified that changeset version
has no issues correctly handling versioning when using the protocol, including bumping the version of packages that depend on workspace packages when that dependency's version is bumped.
I think we should be good to go assuming everything else checks out
@davidkpiano what pnpm version are you on? The lockfile format changed in v8 I think so you might be on an older version
@davidkpiano what pnpm version are you on? The lockfile format changed in v8 I think so you might be on an older version
I might have been on an older version.
Can you fix the conflicts? 🙏
Is there anything else I need to do to move forward with this?
@with-heart this broke VS Code debugging 😢
it now tries to run node_modules/.bin/jest
as javascript file but it's a bash thing created by pnpm, do u know if we can do anything about it?
This PR changes our package manager from
yarn
topnpm
.yarn
withpnpm
inCONTRIBUTING.md
mv scripts/ensure-{yarn,pnpm}.js
and updated test withpnpm/9
patch-package
in place ofpnpm patch
@vue/runtime-dom@3.0.11
as we're on a much newer version that doesn't have the declared globals we had been patchingdevDependencies.xstate
versions toworkspace:^
@manypkg/cli
to latest in order to supportworkspace:
protocolci-setup
yarn
withpnpm
in actions/workflows (exceptdocs
workflow)