chore: migrate to monorepo

[baseballyama]

WIP. Still there are a lot of todos.
-> I will continue work on next weekend. (18th, 19th May)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4425571

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

[baseballyama]

@ota-meshi Almost done but ota-meshi/vite-plugin-eslint4b#51 and ota-meshi/vite-plugin-eslint4b#53 are blocker.
I will do self-review for this but I don't have confident that changeset release works properly or not😅

[baseballyama]

@ota-meshi

I need your help!
Still I can not build docs project due to file path mismatch.

2024-06-08.10.28.24-1.mov

I think ota-meshi/vite-plugin-eslint4b#55 breaks this. But I'm not sure how to solve the issue. Maybe we can revert I think ota-meshi/vite-plugin-eslint4b#55 or you have better idea.

[ota-meshi]

I think ota-meshi/vite-plugin-eslint4b#55 breaks this.

Hmm... It was a CI error so I made some changes. I will check out this branch later and give it a try.

[ota-meshi]

I fixed vite-plugin-eslint4b and I think the build script is passing. However, the playground launched by the dev script still doesn't work. I don't know what the difference is yet...

[baseballyama]

@ota-meshi

Thank you for fixing this!
As far as I know, the dev command is not working properly on the main branch either.
So I think we can merge this PR after completing the following tasks:

• Ensuring that the release process is not broken (since CI cannot check this, we need to verify it manually)
• Conducting a general code review

[baseballyama]

This is not related to this PR, but do you think it is possible to convert the documentation project to ESM?
There are plans to consolidate Svelte-related documentation into a single omnisite, which will need to be migrated to ESM before this can be done.

[ota-meshi]

This is not related to this PR, but do you think it is possible to convert the documentation project to ESM?

Yes, I believe we can migrate our documentation to the ESM project.

[ota-meshi]

Awesome! Thank you for doing a great job!

[baseballyama]

Hum...

[baseballyama]

I'm fixing.

[baseballyama]

Fixed: https://github.com/sveltejs/eslint-plugin-svelte/actions/runs/9427331361/job/25971325775

[baseballyama]

And I confirmed that the site is working properly.