I will be thinking closely and I really prize all thoughtful feedback like this.
we're currently on a collective holiday: https://npmx.dev/recharging. but when we're back, you would be really welcome to join us and make it better - if you want!
npmx maintainer here! a few answers to questions i see:
we haven’t launched yet! we’re building openly but aiming for march 3. as is par for the course, hn gets the scoop.
i made the first commit two weeks ago, so it’s very new. but we’ve had 900+ PRs and 170+ contributors in the last fortnight… because this is something we care about.
having said that, i’m taking notes about what is and isn’t intuitive
npmjs remains the source of truth for the registry, which is why we get our data from there
but along the way we add a lot of features, like:
- claiming new packages from the ui
- batch admin operations for your orgs, teams and packages
- total install size, vulnerabilities and deprecations for your transitive dependencies
- generated docs for packages
- linkable package contents
- and more
it shouldn't need to do this. Nuxt has a @nuxtjs/color-mode module which ensures that the correct colour scheme is applied before the browser starts rendering the html.
the best guarantee I have is that Nuxt is still independent - it's (some of) the core team who are employed by Vercel. you can see this is the case for svelte/sveltekit.
plus, as an open source project, no one _can_ shutter Nuxt. as long as we have a community, we are alive.
from another point of view, any open source project is ultimately accountable to the community, and I think that's especially true for nuxt.
at the end of the day, if sebastien isn't happy with my leadership he can replace me. (and that's _good_ - I wrote about it here: https://roe.dev/blog/governance-and-abuse)
and equally if the community aren't happy with the direction of nuxt, they can always fork it. (and that's _good_)
in fact, I think I'd say that accountability is always good.
there's lots to say here, but from my point of view, Vercel's backing Nuxt largely _because_ of our open vision.
our open approach isn't an optional extra. it's a core value we all share on the team - and indeed, I think, is as close to a core value of the web as I know.
we've pioneered cross-framework adapters and the provider pattern in all we build and there is no way we are changing direction or vision.
nuxt remains an independent framework, like svelte. the fact that a number of us on the team are employed to work full time on OSS is _great_ news for OSS sustainability.
I'm not aware of any issues as long as you are on the latest Nuxt and nuxi versions, so it might be easier to help if you open an issue with a reproduction on https://github.com/nuxt/nuxt/issues.
I will be thinking closely and I really prize all thoughtful feedback like this.
we're currently on a collective holiday: https://npmx.dev/recharging. but when we're back, you would be really welcome to join us and make it better - if you want!
it's open source at https://github.com/npmx-dev/npmx.dev