f868775861
**What** - Move packages for `next` version of admin to core repo **Other** - Since this PR introduces packages that depend on Vite 5, it also introduces @types/node@^20. We have never had a direct dependency on the types package for Node, and as far as I can see that has resulted in us using the types from Node.js@8, as those are a dependency of one of our dependencies. With the introduction of @types/node@^20, two of our packages had TS errors because they were using the NodeJS.Timer type, which was deprecated in Node.js@14. We should add specific @types/node packages to all our packages, but I haven't done so in this PR to keep it as clean as possible. - Q: @olivermrbl I've added the new packages to the ignore list for changeset, is this enough to prevent them from being published?
26 lines
706 B
JSON
26 lines
706 B
JSON
{
|
|
"$schema": "https://unpkg.com/@changesets/config@2.0.0/schema.json",
|
|
"changelog": ["@changesets/changelog-github", { "repo": "medusajs/medusa" }],
|
|
"commit": false,
|
|
"fixed": [],
|
|
"linked": [],
|
|
"access": "public",
|
|
"baseBranch": "develop",
|
|
"updateInternalDependencies": "patch",
|
|
"ignore": [
|
|
"integration-tests-api",
|
|
"integration-tests-plugins",
|
|
"integration-tests-repositories",
|
|
"@medusajs/dashboard",
|
|
"@medusajs/admin-shared",
|
|
"@medusajs/admin-bundler",
|
|
"@medusajs/vite-plugin-extension"
|
|
],
|
|
"snapshot": {
|
|
"useCalculatedVersion": true
|
|
},
|
|
"___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
|
|
"onlyUpdatePeerDependentsWhenOutOfRange": true
|
|
}
|
|
}
|