4 ms·
It's webpack as a service! I would have never guessed that there was a need for this, but maybe there is.
by doix 4y ago
It's webpack as a service! I would have never guessed that there was a need for this, but maybe there is.
- jimhi 4y agoIt’s also completely free for 1 library (which can be used on multiple websites) and you can download the bundle code at any time.
- doix 4y agoMy comment isn't a criticism! I was just confused what you were doing, but now I get it. You run webpack for people and then host the bundle for them. If the title was "Webpack as a service", I would've immediately got it. But I guess your target audience probably wouldn't so your title makes sense for the audience you're targeting + SEO. It would've never occurred to me to make something like this, but after searching for the terms you suggested below, I do see many people asking for this. Telling those people "just setup node/npm/webpack" is probably not helpful. Your service is easier for those people. Nice job identifying a solution for people with a problem!
- yCombLinks 4y agoIt would also be possible to embed components written by others without managing a build toolchain.
- codingdave 4y agoYeah, there probably is a niche that wants this - I would just expect that the people who know how to write the code for React component, but do not know how to bundle it to put on a page is not only a small niche, but an inherently shrinking niche -- why would someone learn to code, but then deliberately skip learning to deploy that code?
- programmarchy 4y agoThe use case is copy and pasting code, not learning how to write the code.