4 ms·
I'm not at all knowledgeable about Vue and its libraries, community, etc., so with a grain of salt, why does it seem that Vue makes Vue versions of various libr
by yladiz 3y ago
I'm not at all knowledgeable about Vue and its libraries, community, etc., so with a grain of salt, why does it seem that Vue makes Vue versions of various libraries, like Vite (Webpack), Vitest (Jest), and now Histoire (Storybook, also an annoying thing to type)? This is not to say that there shouldn't be new tools that compete with existing ones, since generally the more tools the better the ecosystem as a whole is, but it's confusing to me that Vue somehow has this NIH syndrome and new tools crop up specifically for it.
- dcre 3y agoPart of the answer is surely that the tools you’re talking about are dramatic improvements on the originals, speaking as a longtime Webpack and Jest user who now uses Vite and Vitest. Neither is Vue-specific, by the way — I use them with React. (It looks like Histoire doesn’t have a React adapter yet, but I’m sure it will soon.) It seems to me — as someone who uses these tools but has no inside knowledge of the Vue community — that this community just has a really well-developed engineering culture and is producing tools in line with that culture that are all really good and integrate well together. It’s hard to understand why you wouldn’t want that if you could get it!