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
The visual hierarchy seems very flat and inaccessible to me. Everything is monochrome and looks too similar. I have a hard time differentiating between sections.
There are many ways to get more visual hierarchy and I wish you make use of them.
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 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.
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 hope so! The Nuxt adapters and provider pattern are amazing! Its truly impressive how well done it all is and how portable Nuxt is and how other projects have been able to use a lot of the same OSS tech you've created to get portability from the jump.
The portability story for Vercel's own Nextjs is a disaster.
That's nice in theory, but what happens when the inevitable comes and Vercel's grubby little VC hands start squeezing their yoke in order to extract money out of the ecosystem? They're on their Series E last time I checked, that's a lot of VCs who are going to want to cash in on things sooner rather than later.
Enshittification is inevitable when VC is involved in any way whatsoever, so this doesn't strike me as a good thing. I can already see the future where we're getting convoluted features no one ever asked for for the sole reason of inflating Vercel's hosting costs, as was and is the case with Next and how they completely took over React to the point that even the official React docs mention Next before any alternative like Vite. Hell, knowing the VC playbook, I wouldn't be surprised if in a year's time they decide to shutter Nuxt completely and force everyone to move into the abomination that is Next.
This isn't a swipe against you guys, I'm thrilled to see OS devs like you who truly deserve all the success in the world get that success, I'm just not convinced that a VC-funded company with a dubious history & track record monopolizing the entire frontend framework landscape is a good thing. Thankfully Evan seems to still be independent and as such Vue will continue being independent, but it's a bit worrying that it's basically the only one.
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.
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.
Will do once I’ve investigated more. Tried bun yesterday evening and just saw this thread this morning while heading to the lake :)
Thank you for your awesome work on nuxt 3, by the way!
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