Bundle Lexical DevTools with Vite

[noi5e]

This does everything that PR #2388 did, it just creates a browser extension scaffold with Vite instead of Create React App/webpack.

Lots of file/folder structural changes, but not any functional difference for the user. Even the installation instructions in README.md are the same.

I'm still figuring out how to do the Vite config. Right now the assets are split into two folders:

1. src - React components
2. public - I made this folder as a workaround, in order to get Vite to include manifest.json (and everything it references) within the build. Following Vite docs.

It's pretty crucial that the browser extension build includes a manifest.json. It seems like Vite doesn't do this out of the box.

An outside repo makes a custom Vite plugin that will generate a manifest.json, and it looks relatively easy to replicate. I haven't done this yet, will save it for another PR.

---

Developer Tools Web Extension Planning Issue: #2127

[vercel]

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

Name	Status	Preview	Updated
lexical	✅ Ready (Inspect)	Visit Preview	Jun 15, 2022 at 9:25PM (UTC)
lexical-playground	✅ Ready (Inspect)	Visit Preview	Jun 15, 2022 at 9:25PM (UTC)

[noi5e]

I think this should be a simple fix, but I don't have the access to resolve the conflict:

[thegreatercurve]

@noi5e You shouldn't need any kind of special access to resolve the merge conflict. Update main on your fork, and then rebase your branch on top of that before merging into this repo.

[thegreatercurve]

Set up looks fine, but how com we've got rid of TypeScript? That should work out of the box for Vite. See the react-ts example here: https://vitejs.dev/guide/#trying-vite-online

[noi5e]

@thegreatercurve Thanks for the assist, and helping this to pass the CI! Looks like the last few reviews you mentioned were covered by your commit as well.

This might be ready to merge, although I do have a slight question mark about deleting tsconfig.json and if this is now adequately covered by TypeScript from the root config (and not, let's say, from a global install in my environment?). I think it is? But not sure. Dropping a note in chat about this.

[thegreatercurve]

@thegreatercurve Thanks for the assist, and helping this to pass the CI! Looks like the last few reviews you mentioned were covered by your commit as well.

This might be ready to merge, although I do have a slight question mark about deleting tsconfig.json and if this is now adequately covered by TypeScript from the root config (and not, let's say, from a global install in my environment?). I think it is? But not sure. Dropping a note in chat about this.

@noi5e your folder is included in the includes of the base tsconfig, so if running tsc in the root folder doesn't cause any errors, you should be all good!