Skip to content

Releases: tivac/modular-css

Source maps + @values = <3

09 May 06:33
Compare
Choose a tag to compare

Since sourcemaps got some love for v0.20.0 it was finally time to take a look at exposing @value chains in source maps. It ended up not being that hard, so here we go! Now sourcemaps will show you where a value replacement came from, which is really nice!

See #129 for comparison links to the old source maps vs the new, more thorough ones.

Sourcemap fixups!

08 May 06:53
Compare
Choose a tag to compare

Sourcemaps were kinda broken in a bunch of dumb ways. They were broken deep in the core when building the combined CSS file, and the rollup plugin wasn't doing sensible things. Now sourcemaps are reasonable and accurate from the core on out, and the rollup plugin does all the right things so it works as it should.

🎉 🎉 🎉

Browserify symlinks were broken, now they're not

11 Apr 21:03
Compare
Choose a tag to compare

Symlinks were broken when using the browserify plugin due to a strange interaction between the browserify transform and the dependencies pipeline. Fixed it by ensuring that modular-css always use the actual path on disk when building up the dependency graph.

Thanks to @julien-f for reporting #105!

Customizable CWD

09 Mar 00:53
Compare
Choose a tag to compare

v0.13.0 really only adds one feature, a customizable cwd! No longer are you shackled to process.cwd() (although it still defaults to that).

This helped us solve an issue around junctions and relative paths being bunk, who knows what it might solve for you!

Source maps!

25 Jan 23:56
Compare
Choose a tag to compare

v0.11.2 (and v0.11.1, actually) are all about improving the actual day-to-day experience of using modular-css. Now when you are instantiating browserify and you set the debug option you'll automatically get inline sourcemaps in your CSS.

This has also been fixed up so that if you're using the API you can easily enable source maps by passing map : true as an option!

More Promises!

23 Jan 07:38
Compare
Choose a tag to compare

In order for after plugins to be able to fully process the output it was necessary to have .css() (now renamed .output()) return a PostCSS Result or LazyResult instance.

But now stuff like cssnano will work really easily, which is excellent!

Consistent tooling outputs!

22 Jan 06:10
Compare
Choose a tag to compare

So it took some real doing, but browserify/watchify/factor-bundle all should now be fully aware of the CSS dependency graph which means everything should work exactly like you'd expect. That's... not a great selling point, but an improvement over how things were!

Also the CLI now works after the changes in 0.9.x which totally broke things, I apologize!

Promises everywhere!

14 Jan 08:00
Compare
Choose a tag to compare

Wanted to support async postcss plugins like cssnano, which meant I had to rework large parts of the core to use promises for flow control. And now it's done, hooray!

API changes are visible here: https://github.com/tivac/modular-css/blob/v0.9.0/README.md#api

Nicer browserify/watchify behavior

30 Dec 06:12
Compare
Choose a tag to compare

Small release, mostly to fix #32 with #33.

Now when browserify/watchify barfs it'll look better and be way more useful!