Browser friendly npm package

[youknowriad]

In the browser context, dependencies like fs are not necessarily available. Source maps are also not important when the library is used in the browser.

Is this something you could consider: Providing a browser-friendly npm package? I'm well aware about the option here https://github.com/reworkcss/css/blob/master/lib/stringify/index.js#L31 but unfortunately, this can't be statically analyzed by bundlers to avoid bundling the source map file entirely.

Any thoughts?

Thanks.

Context: Trying to use this library in Gutenberg (the new WordPress editor) WordPress/gutenberg#9008

[danielhusar]

We are using it already in browser. (but only parse api)
If you are using webpack, you can do:

node: {
  fs: 'empty',
},

in your webpack config to make it work.

[mangr3n]

Where exactly in the webpack.config.js file does that snippet go? I assume it's not on the root of the config object.

[Ovissse]

Where exactly in the webpack.config.js file does that snippet go? I assume it's not on the root of the config object.

Yes it's on root
https://webpack.js.org/configuration/node/#other-node-core-libraries

[mangr3n]

Thank you

[krzysztof-grzybek]

If you want to use only parser (without stringify), it's possible to run it in browser by importing only parser:

import parser from 'css/lib/parse';

or

const parse = require('css/lib/parse');

[holblin]

I worked on removing the source-map support. This will solve the issue. Trying to reach out to the rework members before going into the fork route (and discussing with my company for the PR route).
ref: #164