chore: move next admin packages to core repo

[kasperkristensen]

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?

[changeset-bot]

🦋 Changeset detected

Latest commit: bcb0554

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
create-medusa-app	Patch
medusa-core-utils	Patch
@medusajs/admin	Patch

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference	⬜️ Ignored (Inspect)	Visit Preview		Jan 8, 2024 9:05am
docs-ui	⬜️ Ignored (Inspect)	Visit Preview		Jan 8, 2024 9:05am
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Jan 8, 2024 9:05am

[olivermrbl]

I've added the new packages to the ignore list for changeset, is this enough to prevent them from being published?

Yes, albeit with two caveats as per the changesets docs:

There are two caveats to this.

- If the package is mentioned in a changeset that also includes a package that is not ignored, publishing will fail.
- If the package requires one of its dependencies to be updated as part of a publish.

But I think we can manage.

Alternatively, we do as with the modules packages and just never include them in changesets.

Or thirdly, add private: true to the package.json 😄

[olivermrbl]

Suggested change

console.log(config1.presets, config2.presets)

[olivermrbl]

Suggested change

console.log("redirecting");

[olivermrbl]

I think you might be missing prettier files to eliminate the semi-colons

[olivermrbl]

Is this a long-running PR? I thought the idea was to merge this, so we can do the follow-up changes in "reviewable" chunks. Happy to do either approach.

[kasperkristensen]

Is this a long-running PR? I thought the idea was to merge this, so we can do the follow-up changes in "reviewable" chunks. Happy to do either approach.

Merging now, I just didn't want to stop work until this was merged, but moving forward each piece of work will be one PR.