Add @lexical/overflow @lexical/link

[trueadm]

This PR removes all the extended nodes from core and instead moves out Links and Overflow nodes to their respective packages instead. I removed ExtendedNodes, as it was leaky and a bit of a temp hack (it should be done on app level, not framework).

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

lexical – ./packages/lexical-website

🔍 Inspect: https://vercel.com/fbopensource/lexical/CbGnnmEcG4WTqQsSaBKHRrQ9sTPy
✅ Preview: https://lexical-git-lexical-link-overflow-fbopensource.vercel.app

lexical-playground – ./packages/lexical-playground

🔍 Inspect: https://vercel.com/fbopensource/lexical-playground/C8uamrLueTwQNXAPzCWKpVvTA1BD
✅ Preview: https://lexical-playground-git-lexical-link-overflow-fbopensource.vercel.app

lexical-website-new – ./packages/lexical-website-new

🔍 Inspect: https://vercel.com/fbopensource/lexical-website-new/H3RWvDSpXLKXe4JKRqMzVaHCLTC8
✅ Preview: https://lexical-website-new-git-lexical-link-overflow-fbopensource.vercel.app

[fantactuka]

Although I like the idea of splitting code into packages, as a library user I'd be a bit annoyed to have to run npm install lexical @lexical/code @lexical/plain .. 10 more ..

For those lazy users, can we do some umbrella package like @lexical/all that has all it as a dependency with re-exports @lexical/all/code.

Maybe installing package is not a bit problem, but then discoverability of API's is quite hard since it's not available until you install all those packages. With bundle package it could be easier by just using IDE's auto suggestion

[trueadm]

@fantactuka Why would they need to do that? They just do npm install @lexical/react and then use the plugins?

[zurfyx]

For those lazy users, can we do some umbrella package like @lexical/all that has all it as a dependency with re-exports @lexical/all/code.

At the same time this plays against our principle of 1 way of doing things, but I do agree with your sentiment. We'll have to make documentation clear.

Probably worth a discussion about this offline too.

[zurfyx]

Accepting as this PR is just following the trend we started weeks ago. We can follow up with a discussion offline

[trueadm]

I don't think is really a big issue. See Babel for an example of how many packages they have, which was hundreds last time I checked. You typically require a core package, which pulls in the others on demand. The issue with @lexical/all is that it promotes a single mega package, which skews npm install times.