chore: update project structure

[jycouet]

• moved folders with git mv ... to preserve git history (please pull and check!)

Gist of the PR

• packages/cli -> packages/sv
• packages/core -> packages/sv/lib/core
• packages/create -> packages/sv/lib/create
• packages/addons -> packages/sv/lib/addons
• packages/cli/commands -> packages/sv/lib/cli

Preparing work for community ;)

[changeset-bot]

⚠️ No Changeset found

Latest commit: e98e09b

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/sveltejs/cli/svelte-migrate@838

npx https://pkg.pr.new/sveltejs/cli/sv@838

commit: e98e09b

[manuel3108]

According to the diff, a few tests got deleted. Any reason why?

Ohhhh, they are re-added in another place. Probably just git fucking around with so many files.

Deleted the change set, as this is not "customer facing" and only internal, similar to the other PRs we merged.

Cool that you managed to keep the testing setup for pnpm test --project core and so on. In the future we could thing about extracting all of the long running "create" and "addon" tests into a seperate package or something, so that you could just run "pnpm test" in the sv directory again. But we can bother about that at a later point.

Also some of these imports became really long, we could consider a path alias or something.

But apart from that, I did not see anything that is not working, so merging this to get it out of the way.

Thanks 🥳