Notices by I use :vim: (asteroidrainfall@fosstodon.org)

@thatonecalculator Just because something is hot and popular doesn't mean you should just jump too it. In industry, there's a lot of that. It's often not worth the time and money to use a new tool without first invalidating what you already have. Hence, why people are still using React over Svelte, JavaScript over TS, DC.js over ECharts.

@thatonecalculator #Webpack is a business requirement at this point.

But maybe a more direct question is, does the library need its own webpack config and should it be built before it's added as a dependency?

Should #NPM libraries handle #bundling themselves?

I'm working in a library for internal use. It will be acting as a utility wrapper for a larger #nodejs library and will be used in two main use cases #CreateReactApp and custom #Webpack projects. This is my first time building a utility library from scratch and was thinking of using Webpack to handle the bundling, tree shaking, and minification, and using #babel for transpiling.

Is this necessary or should this even be done?

#javascript #dev

@rriver フェディバースへようこそ！:fediverse: :ablobcatwave:

@humanetech but it’s more like the merchant side of things rather than the actual storefront from what i can tell. It’s more like a way to synchronize many e-com platforms to a single place. It would be more interesting if it were more like Rakuten, being a platform that acts as a central place for merchants from various platforms to connect with customers.