the new API

[mightyaleksey]

Still, I need to fix trace, but I hope this variant should be better.

[mightyaleksey]

@geelen Can you enlighten me about the destination of the "trace" variable? I figured out, that it should help to predictably load external modules, but I can't understand how it should work properly.

[mightyaleksey]

Okay, I figured it out, how the trace should work 💃

[mightyaleksey]

Anyways, I made that pr in order to unify the implementation between require-hook and css-modulesify and fix few issues: #22, #23, #27, #16

The major change is that it uses the public parser plugin now and I added a flexibility to specify custom loader by providing function through the fetch parameter. So it supports now both loader types: async and sync.
I also updated FileSystemLoader which is used by css-modulesify, so it supports now the new core module and fixes few issues.

[joeybaker]

Just checking in… what's the status on this?

[mightyaleksey]

@joeybaker I want to rework it, but had no free time for that. I'll to make another attempt on the next weekend.

[joshwnj]

good stuff @sullenor - anything we can do to help?

[dfreeman]

@sullenor this looks like it enables some nice stuff for downstream consumers of the loader – any status on when it might land? Anything outsiders can do to help out?

[mightyaleksey]

@joeybaker @joshwnj @dfreeman Hi,

Sorry for the late response. I talked a lot to @ai recently and decided to create a simpler version. I decided to build another two postcss plugins to resolve ICSS :imports and to extract ICSS :exports. So, to use CSS Modules with PostCSS you will need to use the composition of the five plugins.

In my opinion it will provide simpler API for the consumers and it will be easier to share the implementation between different tools (gulp, webpack).

Currently, I almost finished those plugins, so sooner or later I'll be able to send another pr.

[huan086]

@sullenor

I checked out your version of css-modulesify proof-of-concept, css-modules-loader-core the-new-api and postcss-modules-scope absolute-path.

The paths are resolved correctly, but I'm getting the following

Browserify Error { Error: Cannot find module 'folder2\common.css' while parsing file: D:\folder1\folder2\common.css

before any of the plugins I've specified using use gets called. Any idea what is wrong?

[dfreeman]

@sullenor Just checking in again since it's been a few months — how's the implementation on the other plugins looking? Is the idea that this module just becomes a lightweight layer of glue between the various constituent plugins?

[dfreeman]

Time for the quarterly check-in: any movement here, or should we consider this repo more or less abandoned? I'm evaluating just reimplementing Parser in my downstream project and consuming the rest of the PostCSS plugins directly.