Browser support?

Question

Browser support?

Closed this issue 8 years ago · 4 comments

JestDotty commented 8 years ago

Apparently used to be versions of it? But in old readme/gh pages?

normally npm modules have a folder called dist with minified browser versions of a lib

Answer 1 · 2017-03-28T19:43:05.000Z

Anymore I figured the trend was to use Webpack, right?

Answer 2 · 2017-03-28T19:48:51.000Z

... Except I don't use it. This adds extra steps, extra dependencies, and makes it non modular/standalone in design. I thought the whole point of the npm ecosystem was to abstract away the complex and be easy to use. This seems like an anti pattern. I looked at d3 colours and was surprised to find the same issue. However then I found an npm library that supports both (onecolor). I was a little scared; I actually quite love node.js and I was of the opinion the people complaining about how ridiculous the ecosystem is just didn't understand how to use it... I hope we don't predominantly become like that =S

…

On Mar 28, 2017 3:43 PM, "Josh" ***@***.***> wrote: Anymore I figured the trend was to use Webpack, right? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/Qix-/color/issues/111#issuecomment-289882213>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEgscENu6o9P_eciROjrsyYx8rdzyyUfks5rqWLJgaJpZM4MsEWz> .

Answer 3 · 2017-03-28T19:57:39.000Z

cc // @sindresorhus thoughts? Web packaging with NPM isn't my forte - I've never distributed minified versions of my code on NPM.

Answer 4 · 2017-03-29T05:47:05.000Z

I thought the whole point of the npm ecosystem was to abstract away the
complex and be easy to use.

It is and it does, but for Node.js. The browser world is a whole other nightmare.

I was a little scared; I actually quite love node.js and I was of the
opinion the people complaining about how ridiculous the ecosystem is just
didn't understand how to use it...

They clearly don't, but this issue isn't about the Node.js ecosystem, but rather using npm packages in the browser. Not sure why you assume things will just work in the browser. Maybe that will be a good assumption when we all use ES2015 modules everywhere, but that's not the reality today.

It's up to you to handle the browser. The code is all there, but it's up to you to decide how to package it. You could use Webpack or you could use something else. See: sindresorhus/ama#446