Nuxt is being blacklisted? #114
Comments
|
Yes, it was blacklisted due to the high volume of searches for nuxt, which would always fail to build. In any case nuxt is a CLI tool and the concept of bundle size does not have any value here. |
With the growth of server-less solutions exploiting Google-Cloud-Function / AWS Lambda, server-side package size tend to have a real impact on performance (ie: cold start depending a lot on the dependencies loaded). But i agree that may not worth the price to allow people to scan for those big nodejs package. Thank you for the answer. |
|
@pastelsky Could you allow |
|
Though it's just marginal, the error message is also a bit misleading as Nuxt did nothing wrong. It's neither an "evil" package nor involved in suspicious activities 🤷♂️ |
|
And last but not least, all modules containing |
|
Friendly reminder that this is still a very unfortunate solution :( @pastelsky |
|
New year, new try! Friendly reminder @pastelsky |
|
Hi @pastelsky I am the author of Nuxt.js, since v2, we actually splitted I do believe that Nuxt should not be blacklisted anymore, do you mind giving a try please? |
|
@atinux I can assure you that my intention is to keep the blacklist as tiny as possible (hopefully empty in the future). The fact of the matter is, even with nuxt v2, the installation size continues to be a whopping 68MB. I'm not saying this is necessarily a bad thing, since I haven't personally used nuxt, but it is significantly larger than similar packages in the ecosystem, and I don't think its fair for bundlephobia to be allocating so much bandwidth to a single package, given thee resource constraints. |
|
@manniL I've made the regex more specific so that other packages are not affected. This should've been fixed a while back, apologies for the delay. |
|
Thank you @pastelsky for your clarification and answer :) Actually, I was more looking to packagephobia thand bundlephobia but kind of missed it. |
|
+1 for removing Nuxt from the blacklist @pastelsky. Nuxt is a very popular—if not the most popular—framework for developing Vue applications. Bundlephobia is such an awesome site and it makes me sad that I'm not able to use it to compare I don't know how and why Nuxt has an install size of 68mb (perhaps @atinux or @manniL could chime in) but I'd be interested to know how that compares to Next. I know that Nuxt has a fairly healthy Open Collective budget, so if costs for building/hosting Nuxt are a concern, perhaps Nuxt could consider backing this project? |
|
The greater concern is that building `nuxt` with the current webpack
configuration fails every time. If the builds succeed, the cache will
ensure that 68MB isn't as much of a problem. If someone's willing to debug
why webpack fails to build `nuxt`, I'd be happy to remove it from the
blacklist. As a starting point, I'd recommend trying to build `nux` using
the package-build-stats <https://github.com/pastelsky/package-build-stats/>
package.
While `nuxt` is popular, I can't think of a use-case where people would
want to bundle `nuxt` itself with their app. Remember, bundlephobia will
not tell you the size of the app bootstrapped by `nuxt`, but merely the
size of the CLI tool itself.
…On Mon, Feb 11, 2019 at 4:21 PM Matthew Wagerfield ***@***.***> wrote:
+1 for removing Nuxt from the blacklist @pastelsky
<https://github.com/pastelsky>.
Nuxt is a *very* popular—if not the most popular—framework for developing
Vue applications.
Bundlephobia is such an awesome site and it makes me sad that I'm not able
to use it to compare nuxt against the React equivalent of next when
proposing tech stacks to clients.
I don't know how and why Nuxt has an install size of 68mb (perhaps @atinux
<https://github.com/Atinux> or @manniL <https://github.com/manniL> could
chime in) but I'd be interested to know how that compares to Next.
I know that Nuxt has a fairly healthy Open Collective budget, so if costs
for building/hosting Nuxt are a concern, perhaps Nuxt could consider
backing this project?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#114 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIiCHxnKMOV0iHOBj6taJ7k-JjSEOfM9ks5vMUs0gaJpZM4YSwHY>
.
--
Regards,
Shubham Kanodia
|
|
Closing this now that the blacklist has been relaxed to only include Also, the failure message has been improved so that we don't cast any misleading aspersions on |
|
It looks like both Next and Nuxt are blacklisted again.
I agree with this statement. As I mentioned in #40, I came up with a different tool to measure install size which is relevant for CLI tools or backend frameworks. Perhaps it will be relevant to everyone in this thread. |
BUG
Specific package error
Package name
Nuxt
Entire error (stringified) I see in my browser console
code: "BlacklistedPackageError", message: "The package you were looking for is blacklisted due to suspicious activity in the past"Is this intentional?
The current size with dependencies is ~66MB
The text was updated successfully, but these errors were encountered: