Fix some issue in the migration guide

Author: eslachance

README.md

@@ -8,16 +8,16 @@ description: >-
 
 ![Credits: See bottom of page](.gitbook/assets/JOSH\_p\_light.svg)
 
-JOSH is the JavaScript Object Storage Helper - a simple, effective, and efficient database wrapper. The idea of JOSH came out of my existing wrapper, Enmap, which suffers from two very unique but important flaws: 
+JOSH is the JavaScript Object Storage Helper - a simple, effective, and efficient database wrapper. The idea of JOSH came out of my existing wrapper, Enmap, which suffers from two very unique but important flaws:
 
 * It cannot scale very well, being locked to better-sqlite3 which doesn't support live data updates
-* It requires the use of a cache, since most of its features, as used by most people, require the cache to be available. 
+* It requires the use of a cache, since most of its features, as used by most people, require the cache to be available.
 
-JOSH intends to solve both those problems that can't actually be resolved in Enmap itself, by moving away from the synchronous nature of better-sqlite3 and using [Promises](https://js.evie.dev/promises). In this way, JOSH can keep most of Enmap's features but add on a whole lot more. 
+JOSH intends to solve both those problems that can't actually be resolved in Enmap itself, by moving away from the synchronous nature of better-sqlite3 and using [Promises](https://js.evie.dev/promises). In this way, JOSH can keep most of Enmap's features but add on a whole lot more.
 
-Now that this history lesson is done, what exactly _is_ JOSH except being a contrast to something I've already done? 
+Now that this history lesson is done, what exactly _is_ JOSH except being a contrast to something I've already done?
 
-JOSH is a promise-based database wrapper that assists in quick prototyping and rapid development of Node.js applications that require data storage. It aims at removing some of the complexity of database management and communication by providing a _simple_ interface that anyone can pick up and use. 
+JOSH is a promise-based database wrapper that assists in quick prototyping and rapid development of Node.js applications that require data storage. It aims at removing some of the complexity of database management and communication by providing a _simple_ interface that anyone can pick up and use.
 
 JOSH can communicate with many different database systems through the use of _Providers_, which are a translation layer between the JOSH API and the Database system.
 

development/contributing.md

@@ -4,7 +4,7 @@ description: Want to contribute to Josh's development? Please read this page!
 
 # Contributing
 
-I love coding, but sometimes, managing multiple projects can be a tough job. I welcome the contributions of the community to make the experience of using JOSH better. 
+I love coding, but sometimes, managing multiple projects can be a tough job. I welcome the contributions of the community to make the experience of using JOSH better.
 
 ### What can you contribute?
 

development/testing.md

@@ -1,12 +1,12 @@
 # Testing Stuff
 
-If you feel the need to "test" JOSH's functionality from a command line, you're not alone, because I do to! That's why I created a very simple script that lets me directly import and interact with JOSH from the command line. That way I can set, get, delete, and do all the things without having to restart a script every time. 
+If you feel the need to "test" JOSH's functionality from a command line, you're not alone, because I do to! That's why I created a very simple script that lets me directly import and interact with JOSH from the command line. That way I can set, get, delete, and do all the things without having to restart a script every time.
 
-The script uses a simple `readline` module that's core to node, so really the only thing it needs to run is `josh` itself, and a provider such as `@josh-providers/sqlite` . 
+The script uses a simple `readline` module that's core to node, so really the only thing it needs to run is `josh` itself, and a provider such as `@josh-providers/sqlite` .
 
 You'll need to install the appropriate provider, see [Providers ](../providers/about.md)for instructions.
 
-Here's the script: 
+Here's the script:
 
 ```javascript
 const readline = require('readline');

getting-started/faq.md

@@ -12,7 +12,7 @@ Not really. While JOSH does have some features Enmap doesn't (such as providers,
 
 There's a few indications that maybe you'd want to move away from this system.
 
-One of them is if you need more control over the data and how it's stored. JOSH just throws anything you give it into a database, it makes no effort to check, type, or validate that data. 
+One of them is if you need more control over the data and how it's stored. JOSH just throws anything you give it into a database, it makes no effort to check, type, or validate that data.
 
 Another is if you require modelling ("models") or types for your data, as in, very specific limitations on what data can be stored. I've no intention of adding these features.
 

getting-started/install.md

@@ -4,7 +4,7 @@ description: How to install the JOSH Core Database Wrapper
 
 # Installation
 
-JOSH is installed very simply through `yarn` or `npm`: 
+JOSH is installed very simply through `yarn` or `npm`:
 
 ```
 npm i @joshdb/core

getting-started/migrating-from-enmap.md

@@ -6,33 +6,33 @@ description: >-
 
 # Migrating from Enmap
 
-While Josh and Enmap are based on the same basic concepts and ideas, there are some changes that will need to happen in your code if you want to move from Enmap to Josh. 
+While Josh and Enmap are based on the same basic concepts and ideas, there are some changes that will need to happen in your code if you want to move from Enmap to Josh.
 
 A few decisions I made here and there mean that unfortunately, almost all lines related to your database interactions will need to be changed one way or another, so before we start, I apologize from the bottom of my heart that this isn't as straightforward as "change a few lines and import the data". The significant work you'll have to do to convert is entirely my fault, so make sure that you _need_ to move to Josh before you start, otherwise, you're just adding pain onto yourself and I can't take all the blame for that.
 
 ## Why Migrate?
 
-First off: you shouldn't just migrate from Enmap to Josh "just because Josh is newer". Josh isn't an _upgrade_ to Enmap, it's a different module altogether which offers only a few very clear benefit and two downsides that might not be worth it for you. 
+First off: you shouldn't just migrate from Enmap to Josh "just because Josh is newer". Josh isn't an _upgrade_ to Enmap, it's a different module altogether which offers only a few very clear benefit and two downsides that might not be worth it for you.
 
 The first reason why you _should_ migrate, is if you need to access your data from more than one process. For example, if you need to shard a discord.js bot, or if you want a dashboard separated from the bot itself. Or, if you simply have more than one app accessing the same database. Since Enmap doesn't do that (well, it "does" with polling but it's pretty crappy at it), going to Josh is a valid solution.
 
 The second reason you'd want to migrate is if you want to move away from SQLite and want a database server that's more powerful or hosted remotely. Josh offers various providers that give you this capability.
 
 ## Before you migrate
 
-So before you get into this, I would very strongly recommend you get very comfortable with the use of promises. Thing is, where Enmap doesn't use promises at all except for the defer option (which you usually don't need except for specific circumstances), Josh is quite the contrary: _Everything Is Promises_. So, if you don't understand async/await or how to resolve promises you're going to have a bad time. 
+So before you get into this, I would very strongly recommend you get very comfortable with the use of promises. Thing is, where Enmap doesn't use promises at all except for the defer option (which you usually don't need except for specific circumstances), Josh is quite the contrary: _Everything Is Promises_. So, if you don't understand async/await or how to resolve promises you're going to have a bad time.
 
 [The Promise page on my JS guide](https://js.evie.dev/promises) should cover most of the concepts required for you to use Josh so go through that page and then come back. I suggest using async/await whenever possible, and that's how I build all my examples and documentation.
 
 _**MAKE A BACKUP OF YOUR PROJECT NOW**_. If you're using GIT that's simple, just make sure all your changes are commited. If not, just create a zip file or a copy of your project folder (it'll take time unless you delete node\_modules first).
 
 ## Step 1: Installation
 
-The TL;DR of the Installation page is that you just need to run `npm i josh@latest` or `yarn add josh@latest` in your project to get Josh itself. You can simply do this in your project folder, because we can do all this within that folder without losing any data. 
+The TL;DR of the Installation page is that you just need to run `npm i @joshdb/core` or `yarn add @joshdb/core` in your project to get Josh itself. You can simply do this in your project folder, because we can do all this within that folder without losing any data.
 
-Then, you choose a provider and you install that, too, with its pre-requisites. In this example we're going for the SQLite provider, but the instructions should be identical for all of them except for the provider name. So in our case, with the windows-build-tools already installed (because you're using Enmap, you have those already!) we can just `npm i @josh-providers/sqlite` or `yarn add @josh-providers@sqlite` to add it. 
+Then, you choose a provider and you install that, too, with its pre-requisites. In this example we're going for the SQLite provider, but the instructions should be identical for all of them except for the provider name. So in our case, with the windows-build-tools already installed (because you're using Enmap, you have those already!) we can just `npm i @joshdb/sqlite` or `yarn add @joshdb/sqlite` to add it.
 
-With those 2 modules added we can continue on to the migration itself. DO NOT DELETE OR UNINSTALL ENMAP OR ITS DATA YET, obviously.
+With those 2 modules added we can continue on to the migration itself. DO NOT DELETE OR UNINSTALL ENMAP OR ITS DATA YET.
 
 ## Step 2: Migration
 
@@ -65,7 +65,6 @@ const target = new Josh({
 // so we're going to do that with an async IIFE to simplify things.
 // An IIFE is just a function that runs immediately, in this case an async one.
 (async () => {
-  await source.defer;
   console.log(`Loaded Enmap with ${source.count} rows to transfer`);
   console.log(`Target JOSH currently has ${await target.size} rows.`);
 
@@ -83,19 +82,19 @@ Now that the data is completely migrated, we're ready to move on. To verify that
 
 ## Step 3: Changing your Code
 
-Now comes the hard part. You'll need to change your entire code for Josh. This includes every single line where you're getting, setting, or modifying the database. But, there are some general guidelines that will clarify exactly what changes need to be made. 
+Now comes the hard part. You'll need to change your entire code for Josh. This includes every single line where you're getting, setting, or modifying the database. But, there are some general guidelines that will clarify exactly what changes need to be made.
 
 The Initialization
 
-This is an easy one: the initialization for Josh is exactly what you used above in the migration script. You import Josh, the Provider, then you initialize it with the new Josh() line. 
+This is an easy one: the initialization for Josh is exactly what you used above in the migration script. You import Josh, the Provider, then you initialize it with the new Josh() line.
 
 > There is currently no multi() method in Josh, this is in the works, though! For now each instance must be initialized separately.
 
 ### The Key/Path system
 
-In Josh, there is no separate "key" and "path" when it comes to arguments. Basically I realized that with the various arguments between functions, it sometimes was vague or confusing what went where. To simplify this, it's now a single argument that starts each method where a key and/or path is necessary. 
+In Josh, there is no separate "key" and "path" when it comes to arguments. Basically I realized that with the various arguments between functions, it sometimes was vague or confusing what went where. To simplify this, it's now a single argument that starts each method where a key and/or path is necessary.
 
-So, the new system works as a single string, where each part is separated by a dot to indicate a level in the object. Let's see an example with set() first, to, errr, "set the table" as it were. 
+So, the new system works as a single string, where each part is separated by a dot to indicate a level in the object. Let's see an example with set() first, to, errr, "set the table" as it were.
 
 ```javascript
 // In Enmap, you did this: 
@@ -113,7 +112,7 @@ await josh.set("somekey.a", "one");
 
 If you need to access a property that's nested in another level, you can just chain the path exactly as you would have in Enmap, so `await josh.set("somekey.a.foo.bar", "newvalue")` would set at the 3rd level of the object.
 
-Every other method will have the same tweak, from push() and remove() in arrays to get() and has() and all these wonderful things. 
+Every other method will have the same tweak, from push() and remove() in arrays to get() and has() and all these wonderful things.
 
 {% hint style="info" %}
 Since the key/path is a string you can use template literals for variables. For example, in a per-server settings context:
@@ -125,7 +124,7 @@ await client.settings.get(`${message.guild.id}.disabledCommands`);
 
 ### Find, Filter and other loops
 
-Because Josh is not cached in memory, there are a few little changes to the way array methods work. First and foremost it's important to know that for most providers, using the looping methods will cause a significant increase in temporary memory usage (because data still needs to be loaded in memory to be processed in most cases), and using a _path_ rather than a function is going to always be much faster and efficient. In fact, for providers supporting JSON data types (rethink, mongo, postgresql), using path equality means no data is loaded in memory, it's all database-processed and is faster by an order of magnitude. 
+Because Josh is not cached in memory, there are a few little changes to the way array methods work. First and foremost it's important to know that for most providers, using the looping methods will cause a significant increase in temporary memory usage (because data still needs to be loaded in memory to be processed in most cases), and using a _path_ rather than a function is going to always be much faster and efficient. In fact, for providers supporting JSON data types (rethink, mongo, postgresql), using path equality means no data is loaded in memory, it's all database-processed and is faster by an order of magnitude.
 
 {% hint style="info" %}
 Josh support async functions for find(), filter() and some(). However, they will be slower due to "whatever async thing you're doing".

getting-started/usage.md

@@ -1,6 +1,6 @@
 # Basic Usage
 
-\[ TBD ] - Documentation isn't yet ready fully but here's a few examples: 
+\[ TBD ] - Documentation isn't yet ready fully but here's a few examples:
 
 ```javascript
 const Josh = require("@joshdb/core");

providers/indexeddb.md

@@ -12,7 +12,7 @@ There are not provider options with the IndexedDB provider, but an empty option
 
 ### Using with Webpack
 
-To use with Webpack, install with your project: 
+To use with Webpack, install with your project:
 
 ```
 npm i @joshdb/indexeddb

providers/json.md

@@ -18,7 +18,7 @@ yarn add @joshdb/json
 
 ### Usage
 
-Here's how you setup and use the JSON provider: 
+Here's how you setup and use the JSON provider:
 
 ```javascript
 const Josh = require('@joshdb/core');

providers/mongo.md

@@ -61,15 +61,15 @@ Mongo Atlas is a free mongodb hosting service made by, if that wasn't obvious, t
 The setup for Mongo Atlas goes something like this:
 
 * Get an account at [mongodb.com](https://www.mongodb.com/cloud/atlas)
-* Once created, setup your cluster: 
+* Once created, setup your cluster:
   * Provider & Region: Up to you, I chose AWS in my test (but you might have a closer free region!). Make sure to select a "FREE TIER AVAILABLE" region!
   * Keep the M0 cluster tier (the only free one). You may select backups if you want, other additional options are paid.
   * Type in a cluster name of your choice. Something like `guidebot-cluster`.
   * Click **Create Cluster**.
   * Go make a sandwich, setup can take a while...
   * Click the Collection button in the middle of the page.
   * Click Create Database. Enter a name such as `guidebot-session` then a collection name such as `sessions`.
-* Now that the cluster is created, we now need to get a connection string. But we need to create a user, which there's a wizard for. 
+* Now that the cluster is created, we now need to get a connection string. But we need to create a user, which there's a wizard for.
   * Click **Command Line Tools** at the top of the cluster window, then click **Connect Instructions**.
   * Click **Add your Current IP** if you're on the machine that will host your bot. Otherwise, click **Add a Different IP Address** and enter it on the left. Click **Add IP Address**.
   * Enter a database access _username_ and _password_, then click **Create MongoDB User**.

providers/sqlite.md

@@ -6,7 +6,7 @@ description: >-
 
 # SQLite
 
-SQLite communication is provided by better-sqlite3. 
+SQLite communication is provided by better-sqlite3.
 
 This provider requires building better-sqlite3 from source, so you'll need to make sure your system is ready for that.