You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug-report.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ A clear and concise description of what the bug is.
17
17
18
18
The _minimal_ information needed to reproduce your issue (ideally a package.json with a single dep). Note that bugs without minimal reproductions might be closed.
19
19
20
-
IMPORTANT: We strongly prefer reproductions that use Sherlock. Please check our documentation for more information: https://next.yarnpkg.com/advanced/sherlock
20
+
IMPORTANT: We strongly prefer reproductions that use Sherlock. Please check our documentation for more information: https://yarnpkg.com/advanced/sherlock
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Remember that a [migration guide](https://yarnpkg.com/advanced/migration) is ava
28
28
29
29
- The Yarn configuration has been revamped and *will not read the `.npmrc` files anymore.* This used to cause a lot of confusion as to where the configuration was coming from, so the logic is now very simple: Yarn will look in the current directory and all its ancestors for `.yarnrc.yml` files.
30
30
31
-
- Note that the configuration files are now called `.yarnrc.yml` and thus are expected to be valid YAML. The available settings are listed [here](https://next.yarnpkg.com/configuration/yarnrc).
31
+
- Note that the configuration files are now called `.yarnrc.yml` and thus are expected to be valid YAML. The available settings are listed [here](https://yarnpkg.com/configuration/yarnrc).
32
32
33
33
- The lockfiles now generated should be compatible with Yaml, while staying compatible with old-style lockfiles. Old-style lockfiles will be automatically migrated, but that will require some round-trips to the registry to obtain more information that wasn't stored previously, so the first install will be slightly slower.
34
34
@@ -38,7 +38,7 @@ Remember that a [migration guide](https://yarnpkg.com/advanced/migration) is ava
38
38
39
39
### Package manifests (`package.json`)
40
40
41
-
To see a comprehensive documentation about each possible field, please check our [documentation](https://next.yarnpkg.com/configuration/manifest).
41
+
To see a comprehensive documentation about each possible field, please check our [documentation](https://yarnpkg.com/configuration/manifest).
42
42
43
43
- Two new fields are now supported in the `publishConfig` key of your manifests: the `main`, `bin`, and `module` fields will be used to replace the value of their respective top-level counterparts in the manifest shipped along with the generated file.
Copy file name to clipboardExpand all lines: README.md
+13-13
Original file line number
Diff line number
Diff line change
@@ -21,18 +21,18 @@ Yarn is a modern package manager split into various packages. Its novel architec
21
21
22
22
- Yarn supports plugins; adding a plugin is as simple as adding it into your repository
23
23
- Yarn supports Node by default but isn't limited to it - plugins can add support for other languages
24
-
- Yarn supports [workspaces](https://next.yarnpkg.com/features/workspaces) natively, and its CLI takes advantage of that
24
+
- Yarn supports [workspaces](https://yarnpkg.com/features/workspaces) natively, and its CLI takes advantage of that
25
25
- Yarn uses a portable shell to execute package scripts, guaranteeing they work the same way on Windows and Linux
26
26
- Yarn is first and foremost a Node API that can be used programmatically (via [@yarnpkg/core](packages/yarnpkg-core))
27
27
- Yarn is written in TypeScript, and is fully type checked
28
28
29
29
## Install
30
30
31
-
Consult the [dedicated page](https://next.yarnpkg.com/getting-started/install) for more details.
31
+
Consult the [dedicated page](https://yarnpkg.com/getting-started/install) for more details.
32
32
33
33
## Documentation
34
34
35
-
The documentation is being reworked to contain an updated content and a refreshed design, and the most up-to-date version can be found on the repository GitHub pages: [next.yarnpkg.com](https://next.yarnpkg.com/)
35
+
The documentation is being reworked to contain an updated content and a refreshed design, and the most up-to-date version can be found on the repository GitHub pages: [yarnpkg.com](https://yarnpkg.com/)
36
36
37
37
## Current status
38
38
@@ -85,34 +85,34 @@ Note that no other command is needed! Given that our dependencies are checked-in
85
85
Those plugins typically come bundled with Yarn. You don't need to do anything special to use them.
86
86
87
87
-[★ plugin-constraints](packages/plugin-constraints) adds support for `yarn constraints [--fix]`.
88
-
-[★ plugin-dlx](packages/plugin-dlx) adds support for the [`yarn dlx`](https://next.yarnpkg.com/cli/dlx) command.
88
+
-[★ plugin-dlx](packages/plugin-dlx) adds support for the [`yarn dlx`](https://yarnpkg.com/cli/dlx) command.
89
89
-[★ plugin-essentials](packages/plugin-essentials) adds various commands deemed necessary for a package manager (add, remove, ...).
90
90
-[★ plugin-file](packages/plugin-file) adds support for using the `file:` protocol within your dependencies.
91
91
-[★ plugin-github](packages/plugin-github) adds support for using Github references as dependencies. [This plugin doesn't use git.](https://stackoverflow.com/a/13636954/880703)
92
92
-[★ plugin-http](packages/plugin-http) adds support for using straight URL references as dependencies (tgz archives only).
93
-
-[★ plugin-init](packages/plugin-init) adds support for the [`yarn init`](https://next.yarnpkg.com/cli/init) command.
93
+
-[★ plugin-init](packages/plugin-init) adds support for the [`yarn init`](https://yarnpkg.com/cli/init) command.
94
94
-[★ plugin-link](packages/plugin-link) adds support for using `link:` and `portal:` references as dependencies.
95
95
-[★ plugin-npm](packages/plugin-npm) adds support for using [semver ranges](https://semver.org) as dependencies, resolving them to an NPM-like registry.
96
-
-[★ plugin-npm-cli](packages/plugin-npm-cli) adds support for the NPM-specific commands ([`yarn npm login`](https://next.yarnpkg.com/cli/npm/login), [`yarn npm publish`](https://next.yarnpkg.com/cli/npm/publish), ...).
97
-
-[★ plugin-pack](packages/plugin-pack) adds support for the [`yarn pack`](https://next.yarnpkg.com/cli/pack) command.
98
-
-[★ plugin-pnp](packages/plugin-pnp) adds support for installing Javascript dependencies through the [Plug'n'Play](https://next.yarnpkg.com/features/pnp) specification.
96
+
-[★ plugin-npm-cli](packages/plugin-npm-cli) adds support for the NPM-specific commands ([`yarn npm login`](https://yarnpkg.com/cli/npm/login), [`yarn npm publish`](https://yarnpkg.com/cli/npm/publish), ...).
97
+
-[★ plugin-pack](packages/plugin-pack) adds support for the [`yarn pack`](https://yarnpkg.com/cli/pack) command.
98
+
-[★ plugin-pnp](packages/plugin-pnp) adds support for installing Javascript dependencies through the [Plug'n'Play](https://yarnpkg.com/features/pnp) specification.
99
99
100
100
### Contrib plugins
101
101
102
102
Although developed on the same repository as Yarn itself, those plugins are optional and need to be explicitly installed through `yarn plugin import @yarnpkg/<plugin-name>`.
103
103
104
104
-[☆ plugin-exec](packages/plugin-exec) adds support for using the `exec:` protocol within your dependencies.
105
-
-[☆ plugin-stage](packages/plugin-stage) adds support for the [`yarn stage`](https://next.yarnpkg.com/cli/stage) command.
105
+
-[☆ plugin-stage](packages/plugin-stage) adds support for the [`yarn stage`](https://yarnpkg.com/cli/stage) command.
106
106
-[☆ plugin-typescript](packages/plugin-typescript) improves the user experience when working with TypeScript.
107
-
-[☆ plugin-workspace-tools](packages/plugin-workspace-tools) adds support for the [`yarn workspaces foreach`](https://next.yarnpkg.com/cli/workspaces/foreach) command.
107
+
-[☆ plugin-workspace-tools](packages/plugin-workspace-tools) adds support for the [`yarn workspaces foreach`](https://yarnpkg.com/cli/workspaces/foreach) command.
108
108
109
109
### Third-party plugins
110
110
111
-
Plugins can be developed by third-party entities. To use them within your applications, just specify the full plugin URL when calling [`yarn plugin import`](https://next.yarnpkg.com/cli/plugin/import). Note that plugins aren't fetched from the npm registry at this time - they must be distributed as a single JavaScript file.
111
+
Plugins can be developed by third-party entities. To use them within your applications, just specify the full plugin URL when calling [`yarn plugin import`](https://yarnpkg.com/cli/plugin/import). Note that plugins aren't fetched from the npm registry at this time - they must be distributed as a single JavaScript file.
112
112
113
113
### Creating a new plugin
114
114
115
-
To create your own plugin, please refer to the [documentation](https://next.yarnpkg.com/features/plugins).
115
+
To create your own plugin, please refer to the [documentation](https://yarnpkg.com/features/plugins).
116
116
117
117
## Generic packages
118
118
@@ -123,7 +123,7 @@ The following packages are generic and can be used in a variety of purposes (inc
123
123
-[@yarnpkg/json-proxy](packages/yarnpkg-json-proxy) allows to temporarily convert any POD object to an immutable object.
124
124
-[@yarnpkg/libzip](packages/yarnpkg-libzip) contains zlib+libzip bindings compiled to WebAssembly.
125
125
-[@yarnpkg/parsers](packages/yarnpkg-parsers) can be used to parse the language used by [@yarnpkg/shell](packages/yarnpkg-shell).
126
-
-[@yarnpkg/pnp](packages/yarnpkg-pnp) can be used to generate [Plug'n'Play](https://next.yarnpkg.com/features/pnp)-compatible hooks.
126
+
-[@yarnpkg/pnp](packages/yarnpkg-pnp) can be used to generate [Plug'n'Play](https://yarnpkg.com/features/pnp)-compatible hooks.
127
127
-[@yarnpkg/pnpify](packages/yarnpkg-pnpify) is a CLI tool to transparently add PnP support to various tools.
128
128
-[@yarnpkg/shell](packages/yarnpkg-shell) is a portable bash-like shell interpreter.
0 commit comments