Move all solidjs modules under @solidjs npm scope

[trivikr]

This idea was originally discussed on Discord Thread.

The core module solid-js can be republished under say @solidjs/solid, and there would be a standard followed across GitHub and Npm.

You can also republish:

• solid-js/web under @solidjs/web
• solid-ssr under @solidjs/ssr
• solid-element under @solidjs/element
• solid-app-router under @solidjs/app-router or @solidjs/router
• solid-styled-components to @solidjs/styled-components

Community maintained packages (like @amoutonbrady/solid-heroicons) can be also be published under @solidjs/heroicons if maintainers are ok with it.

[trivikr]

Update as of 08/19:

• Core maintainers @ryansolid and @davedbase are onboard to the idea.
• The org name solidjs is not available on npm.
• Npm currently has a freeze on organization transfers for squatted/abandoned packages.
• Created a discussion thread on official npm feedback channel for timeline on when process is going to be updated.
• Sent an email to npm Support requesting for timeline. They responded stating that the request for solidjs org name is under review, and they'll get back.

[trivikr]

Suggestion from Discord: Use @solidjs/core instead of @solidjs/solid for solid-js.

Similar to other examples:

• @babel/core (29M weekly downloads)
• @jest/core (11M weekly downloads)
• @popperjs/core (4.2M weekly downloads)
• @storybook/core (2.8M weekly downloads)
• @angular/core (2.5M weekly downloads)
• @material-ui/core (2M weekly downloads)

[ryansolid]

Angular is the only framework in that list.. let's see @stencil/core. Oh know what does suck the module subnesting we do..

@solidjs/core/web @solidjs/core/stores Hmm.. timing of doing this is pretty critical. Honestly I don't think we could pull this sort of move until a major version change. Anything else is fine since nothing else is 1.0.

[trivikr]

@solidjs/core/web @solidjs/core/stores

I would suggest using @solidjs/web and @solidjs/stores instead.

Honestly I don't think we could pull this sort of move until a major version change.

True. Using scope should be reserved for v2.0.0. May be plan it for early 2022?

[ryansolid]

Yeah currently they are part of the same repo. I always liked how Preact kept that tight. I've always modelled things closer to them than say Angular.

Yeah we'll see. I don't want to spend a major version until there is a good reason for breaking changes. I imagine there will be 2 more minor versions this fall. We will see where things are after that. Honestly if everything moved except the core package for now we are still in really good shape.

[orenelbaum]

@solidjs/core/web @solidjs/core/stores

I would suggest using @solidjs/web and @solidjs/stores instead.

I like this. I think that from a user perspective having web its own thing, separate from the reactivity modules, would make more sense.

[trivikr]

Update as of 01/23: The solidjs org name on npm was transferred to me in response to support request to npm.
I've transferred it to @ryansolid - creator of SolidJS.

[trivikr]

As per previous discussions, moving to solidjs scope will mostly be prioritized for next major version bump, i.e. 2.0
The SolidJS core team may consider publishing packages under both solid-* and @solidjs/* names prior to 2.0 release.