WIP: fix some of the rename issues

Author: tivac

README.md

@@ -87,37 +87,37 @@ More detailed descriptions are available in [docs/features.md](docs/features.md)
 ### [JS API](/packages/core/#readme)
 
 ```bash
-$ npm i modular-css-core
+$ npm i @modular-css/processor
 ```
 
 ### [CLI](/packages/cli/#readme)
 
 ```bash
-$ npm i modular-css-cli
+$ npm i @modular-css/cli
 ```
 
 ### [Browserify](/packages/browserify/#readme)
 
 ```bash
-$ npm i modular-cssify
+$ npm i @modular-css/browserify
 ```
 
 ### [Rollup](/packages/rollup/#readme)
 
 ```bash
-$ npm i modular-css-rollup
+$ npm i @modular-css/rollup
 ```
 
 ### [Webpack](/packages/webpack/#readme)
 
 ```bash
-$ npm i modular-css-webpack
+$ npm i @modular-css/webpack
 ```
 
 ### [Svelte](/packages/svelte/#readme)
 
 ```bash
-$ npm i modular-css-svelte
+$ npm i @modular-css/svelte
 ```
 
 ### [PostCSS Plugin](/packages/postcss/#readme)
@@ -129,7 +129,7 @@ $ npm i postcss-modular-css
 ### [Globbing API](/packages/glob/#readme)
 
 ```bash
-$ npm i modular-css-glob
+$ npm i @modular-css/glob
 ```
 
 ## Why?

docs/api.md

@@ -111,7 +111,7 @@ new Processor({
 // or
 
 new Processor({
-    namer : "modular-css-namer"
+    namer : "@modular-css/shortnames"
 });
 ```
 
@@ -131,7 +131,7 @@ Resolver functions should either return an absolute path or a falsey value. They
 new Processor({
     resolvers : [
         (src, file, resolve) => ...,
-        require("modular-css-resolvepaths")(
+        require("@modular-css/path-resolver")(
             "./some/other/path"
         )
     ]

docs/browserify.md

@@ -1,8 +1,8 @@
 # Browserify
 
-`modular-cssify` provides a browserify plugin that exposes `modular-css` functionality. It can also be combined with the `factor-bundle` plugin to output a common CSS file as well as bundle-specific CSS files.
+`@modular-css/browserify` provides a browserify plugin that exposes `modular-css` functionality. It can also be combined with the `factor-bundle` plugin to output a common CSS file as well as bundle-specific CSS files.
 
-The `modular-cssify` plugin will use the `basedir` passed to browserify as it's `cwd` parameter.
+The `@modular-css/browserify` plugin will use the `basedir` passed to browserify as it's `cwd` parameter.
 
 ## Options
 
@@ -21,7 +21,7 @@ All other options are passed to the underlying `Processor` instance, see [Option
 ## CLI
 
 ```
-$ browserify -p [ modular-cssify --css "./style.css" ] entry.js
+$ browserify -p [ @modular-css/browserify --css "./style.css" ] entry.js
 ```
 
 ## API
@@ -32,22 +32,22 @@ var browserify = require("browserify"),
 
 build = browserify("./entry.js");
 
-build.plugin("modular-cssify", {
+build.plugin("@modular-css/browserify", {
     css : "./style.css",
 });
 ```
 
 ## `factor-bundle`
 
-The `modular-cssify` is fully `factor-bundle` aware and will output correctly-partitioned CSS bundles to match the JS bundles created by `factor-bundle`.
+The `@modular-css/browserify` is fully `factor-bundle` aware and will output correctly-partitioned CSS bundles to match the JS bundles created by `factor-bundle`.
 
-**WARNING**: Due to how `factor-bundle` works the `modular-cssify` plugin must be applied to the Browserify object **before** `factor-bundle`.
+**WARNING**: Due to how `factor-bundle` works the `@modular-css/browserify` plugin must be applied to the Browserify object **before** `factor-bundle`.
 
 ### CLI
 
 ```
 $ browserify home.js account.js \
-    -p [ modular-cssify --css gen/common.css ] \
+    -p [ @modular-css/browserify --css gen/common.css ] \
     -p [ factor-bundle -o gen/home.js -o gen/account.js ] \
     -o bundle/common.js
 ```
@@ -61,7 +61,7 @@ var build = browserify([
     ]);
 
 // NOTE modular-css applied before factor-bundle, it won't work otherwise!
-build.plugin("modular-cssify", {
+build.plugin("@modular-css/browserify", {
     css : "./gen/common.css"
 });
 

docs/cli.md

@@ -3,7 +3,7 @@
 ## Installation
 
 ```bash
-$ npm i modular-css-cli
+$ npm i @modular-css/cli
 ```
 
 ## Usage

docs/glob.md

@@ -5,7 +5,7 @@ If you don't care about the dependency tree from your code you can also use the
 ## Usage
 
 ```js
-var glob = require("modular-css-glob");
+var glob = require("@modular-css/glob");
 
 glob({
     search : [

docs/namer.md

@@ -1,4 +1,4 @@
-# modular-css-namer
+# @modular-css/shortnames
 
 A [`namer`](./api.md#namer) function to provide tiny classnames for production builds.
 

docs/paths.md

@@ -1,4 +1,4 @@
-modular-css-paths [![NPM Version](https://img.shields.io/npm/v/modular-css-paths.svg)](https://www.npmjs.com/package/modular-css-paths) [![NPM License](https://img.shields.io/npm/l/modular-css-paths.svg)](https://www.npmjs.com/package/modular-css-paths) [![NPM Downloads](https://img.shields.io/npm/dm/modular-css-paths.svg)](https://www.npmjs.com/package/modular-css-paths)
+@modular-css/path-resolver [![NPM Version](https://img.shields.io/npm/v/@modular-css/path-resolver.svg)](https://www.npmjs.com/package/@modular-css/path-resolver) [![NPM License](https://img.shields.io/npm/l/@modular-css/path-resolver.svg)](https://www.npmjs.com/package/@modular-css/path-resolver) [![NPM Downloads](https://img.shields.io/npm/dm/@modular-css/path-resolver.svg)](https://www.npmjs.com/package/@modular-css/path-resolver)
 ===========
 
 A resolver for `modular-css` that will let you resolve file references against arbitrary paths. Useful to avoid code like
@@ -11,15 +11,15 @@ which is annoying to write, annoying to read, and also super-brittle.
 
 ## Install
 
-`$ npm i modular-css-paths`
+`$ npm i @modular-css/path-resolver`
 
 ## Usage
 
 Pass as part of the `resolvers` array in the `modular-css` options (via JS API/Rollup/Browserify/WebPack/etc). When `modular-css` is trying to resolve `@value` or `composes` file references it'll use the default node resolution algorithm against whichever paths you specified.
 
 ```js
-var Processor = require("modular-css-core"),
-    paths     = require("modular-css-paths")
+var Processor = require("@modular-css/processor"),
+    paths     = require("@modular-css/path-resolver")
 
     processor = new Processor({
         resolvers : [

docs/rollup.md

@@ -1,17 +1,17 @@
-# modular-css-rollup
+# @modular-css/rollup
 
 Rollup support for [`modular-css`](https://github.com/tivac/modular-css).
 
 ## Install
 
-`$ npm i modular-css-rollup`
+`$ npm i @modular-css/rollup`
 
 ## ⚠️Rollup Version support⚠️
 
 Due to API changes, certain major versions of this plugin will require a specific minimum rollup version.
 
-- `modular-css-rollup@11` requires `rollup@0.60.0`
-- `modular-css-rollup@15` requires `rollup@0.65.0`
+- `@modular-css/rollup@11` requires `rollup@0.60.0`
+- `@modular-css/rollup@15` requires `rollup@0.65.0`
 
 ## Usage
 
@@ -21,15 +21,15 @@ Due to API changes, certain major versions of this plugin will require a specifi
 const bundle = await rollup({
     input   : "./index.js",
     plugins : [
-        require("modular-css-rollup")()
+        require("@modular-css/rollup")()
     ]
 });
 ```
 
 ### Config file
 
 ```js
-import css from "modular-css-rollup";
+import css from "@modular-css/rollup";
 
 export default {
     input   : "./index.js",

docs/svelte.md

@@ -1,6 +1,6 @@
 # Svelte
 
-`modular-css-svelte` provides a [svelte preprocessor](https://svelte.technology/guide#preprocessing) that can convert inline `<style>` or external `<link>` tags using `modular-css` and will also staticly replace any css references it can find for maximum speed.
+`@modular-css/svelte` provides a [svelte preprocessor](https://svelte.technology/guide#preprocessing) that can convert inline `<style>` or external `<link>` tags using `modular-css` and will also staticly replace any css references it can find for maximum speed.
 
 ### Options
 
@@ -13,7 +13,7 @@ All options are passed to the underlying `Processor` instance, see [Options](api
 ```js
 const filename = "./Component.html";
 
-const { processor, preprocess } = require("modular-css-svelte")({
+const { processor, preprocess } = require("@modular-css/svelte")({
     // Processor options
 });
 
@@ -27,14 +27,14 @@ const result = processor.output();
 fs.writeFileSync("./dist/bundle.css", result.css);
 ```
 
-### `modular-css-rollup`
+### `@modular-css/rollup`
 
 #### API
 
 ```js
 const rollup = require("rollup").rollup;
 
-const { preprocess, processor } = require("modular-css-svelte")({
+const { preprocess, processor } = require("@modular-css/svelte")({
     // Processor options
 });
 
@@ -46,7 +46,7 @@ const bundle = await rollup({
             preprocess,
         }),
 
-        require("modular-css-rollup")({
+        require("@modular-css/rollup")({
             processor,
 
             common : "common.css",
@@ -64,7 +64,7 @@ bundle.write({
 #### `rollup.config.js`
 
 ```js
-const { preprocess, processor } = require("modular-css-svelte")({
+const { preprocess, processor } = require("@modular-css/svelte")({
     // Processor options
 });
 
@@ -81,7 +81,7 @@ module.exports = {
             preprocess,
         }),
 
-        require("modular-css-rollup")({
+        require("@modular-css/rollup")({
             processor,
 
             common : "common.css",

docs/webpack.md

@@ -12,7 +12,7 @@ You will need to use **both** in tandem for things to work!
 // webpack.config.js
 var path = require("path"),
 
-    CSSPlugin = require("modular-css-webpack/plugin");
+    CSSPlugin = require("@modular-css/webpack/plugin");
 
 module.exports = {
     entry   : "./input.js",
@@ -24,14 +24,14 @@ module.exports = {
         rules : [
             {
                 test : /\.css$/,
-                use  : "modular-css-webpack/loader"
+                use  : "@modular-css/webpack/loader"
             },
 
             // Or with loader options
             {
                 test : /\.css$/,
                 use : {
-                    loader  : "modular-css-webpack/loader",
+                    loader  : "@modular-css/webpack/loader",
                     options : {
                         namedExports : false
                     }

jest.config.js

@@ -11,7 +11,7 @@ module.exports = {
     coveragePathIgnorePatterns : [
       "/node_modules/",
       "/parsers/",
-      "/test-utils/",
+      "/@modular-css/test-utils/",
     ],
 
     watchPathIgnorePatterns : [