From 9d48da4483946def5276bedb36b2d37dc87d51ed Mon Sep 17 00:00:00 2001 From: Adarsh Konchady Date: Thu, 2 Mar 2023 22:40:50 -0600 Subject: [PATCH] Fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 68fd514..6d3bec0 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ When developing and authoring multiple packages (private or public), you often f - `yalc` acts as very simple local repository for your locally developed packages that you want to share across your local environment. - When you run `yalc publish` in the package directory, it grabs only files that should be published to NPM and _puts_ them in a special global store (located, for example, in `~/.yalc`). -- When you run `yalc add my-package` in your `project` it _pulls_ package content into `.yalc` in the current folder and injects a `file:`/`link:` dependency into `package.json`. Alternatively, you may use `yalc link my-package` which will create a symlink to the package content in `node_modules` and will not touch `package.json` (like `npm/yarn link` does), or you even may use it with **Pnmp/Yarn/Npm workspaces**. +- When you run `yalc add my-package` in your `project` it _pulls_ package content into `.yalc` in the current folder and injects a `file:`/`link:` dependency into `package.json`. Alternatively, you may use `yalc link my-package` which will create a symlink to the package content in `node_modules` and will not touch `package.json` (like `npm/yarn link` does), or you even may use it with **Pnpm/Yarn/Npm workspaces**. - `yalc` creates a special `yalc.lock` file in your project (similar to `yarn.lock` and `package-lock.json`) that is used to ensure consistency while performing `yalc`'s routines. - `yalc` can be used with projects where `yarn` or `npm` package managers are used for managing `package.json` dependencies.