Update documentation

README.md

@@ -112,7 +112,7 @@ or, using yarn
 yarn add --dev @ianvs/prettier-plugin-sort-imports
 ```
 
-**Note: If you are migrating from v2.x.x to v3.x.x, [Please Read Migration Guidelines](./docs/MIGRATION.md)**
+**Note: If you are migrating from v3.x.x to v4.x.x, [Please Read Migration Guidelines](./docs/MIGRATION.md)**
 
 ## Usage
 
@@ -128,7 +128,7 @@ module.exports = {
     trailingComma: 'all',
     singleQuote: true,
     semi: true,
-    importOrder: ['^@core/(.*)$', '^@server/(.*)$', '^@ui/(.*)$', '^[./]'],
+    importOrder: ['^@core/(.*)$', '', '^@server/(.*)$', '', '^@ui/(.*)$', '', '^[./]'],
     importOrderCaseInsensitive: true,
     importOrderParserPlugins: ['typescript', 'jsx', 'decorators-legacy'],
     importOrderMergeDuplicateImports: true,

docs/MIGRATION.md

@@ -7,6 +7,34 @@
 - The `importOrderBuiltinModulesToTop` option has been removed, and node.js built in modules are always sorted to the top.
 - The `importOrderSeparation` option has been removed.  Use empty quotes in your `importOrder` to control the placement of blank lines.
 
+#### `importOrderSeparation` removed
+
+This option was removed to simplify the configuration of the plugin. But if you like to separate your import groups with newlines, you can do so by adding `""` groups to your `importOrder` array.
+
+For example:
+
+```js
+    "importOrder": [
+        "", // This emptry group at the start will separate side-effects
+        "<THIRD_PARTY_MODULES>",
+        "",
+        "^@app/(.*)$",
+        "",
+        "^[./]"
+    ]
+```
+
+Or, if you would like to keep all imports together, but add a newline before side-effect imports:
+
+```js
+    "importOrder": [
+        "<THIRD_PARTY_MODULES>",
+        "^@app/(.*)$",
+        "^[./]"
+        "", // This will add a newline between side-effect groups (i.e. the chunks that are sorted)
+    ]
+```
+
 ### Migrating from v2.x.x to v3.x.x
 
 #### TL;DR