diff --git a/.eslintignore b/.eslintignore index bdfdfaeab2388d..19e0fcee9e1b5a 100644 --- a/.eslintignore +++ b/.eslintignore @@ -1,5 +1,4 @@ node_modules -lib/internal/v8_prof_polyfill.js lib/punycode.js test/addons/??_* test/fixtures diff --git a/.eslintrc.js b/.eslintrc.js index af1249eae6436e..010c02be11bcf4 100644 --- a/.eslintrc.js +++ b/.eslintrc.js @@ -18,6 +18,7 @@ const hacks = [ 'eslint-plugin-markdown', '@babel/eslint-parser', '@babel/plugin-syntax-class-properties', + '@babel/plugin-syntax-top-level-await', ]; Module._findPath = (request, paths, isMain) => { const r = ModuleFindPath(request, paths, isMain); @@ -41,7 +42,10 @@ module.exports = { parser: '@babel/eslint-parser', parserOptions: { babelOptions: { - plugins: [Module._findPath('@babel/plugin-syntax-class-properties')], + plugins: [ + Module._findPath('@babel/plugin-syntax-class-properties'), + Module._findPath('@babel/plugin-syntax-top-level-await'), + ], }, requireConfigFile: false, sourceType: 'script', @@ -53,6 +57,7 @@ module.exports = { 'doc/api/module.md', 'doc/api/modules.md', 'doc/api/packages.md', + 'doc/api/wasi.md', 'test/es-module/test-esm-type-flag.js', 'test/es-module/test-esm-type-flag-alias.js', '*.mjs', diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 66efca5cd000e7..56632fda4c67eb 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,21 +1,15 @@ - -##### Checklist - +For code changes: +1. Include tests for any bug fixes or new features. +2. Update documentation if relevant. +3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes. -- [ ] `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes -- [ ] tests and/or benchmarks are included -- [ ] documentation is changed or added -- [ ] commit message follows [commit guidelines](https://github.com/nodejs/node/blob/master/doc/guides/contributing/pull-requests.md#commit-message-guidelines) - - unpublish policies
npm unpublish [<@scope>/]<pkg>@<version>
@@ -152,16 +153,21 @@ npm unpublish [<@scope>/]<pkg> --force
Consider using the deprecate
command instead, if your intent is to encourage users to upgrade, or if you no longer want to maintain a package.
Consider using the deprecate
command instead,
+if your intent is to encourage users to upgrade, or if you no longer
+want to maintain a package.
This removes a package version from the registry, deleting its -entry and removing the tarball.
-If no version is specified, or if all versions are removed then -the root package entry is removed from the registry entirely.
-Even if a package version is unpublished, that specific name and -version combination can never be reused. In order to publish the -package again, a new version number must be used. If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed.
-To learn more about how unpublish is treated on the npm registry, see our unpublish policies.
+This removes a package version from the registry, deleting its entry and +removing the tarball.
+The npm registry will return an error if you are not logged +in.
+If you do not specify a version or if you remove all of a package’s +versions then the registry will remove the root package entry entirely.
+Even if you unpublish a package version, that specific name and version +combination can never be reused. In order to publish the package again, +you must use a new version number. If you unpublish the entire package, +you may not publish any new versions of that package until 24 hours have +passed.
npm <command> [args]
7.3.0
+7.4.3
npm is the package manager for the Node JavaScript platform. It puts modules in place so that node can find them, and manages dependency @@ -246,19 +246,10 @@
Patches welcome!
If you would like to contribute, but don’t know what to work on, read -the contributing guidelines and check the issues list.
- +the contributing guidelines +and check the issues list.When you find issues, please report them:
-When you find issues, please report them: https://github.com/npm/cli/issues
Be sure to follow the template and bug reporting guidelines.
Discuss new feature ideas on our discussion forum:
@@ -269,11 +260,6 @@Isaac Z. Schlueter :: -isaacs :: -@izs :: -i@izs.me
To publish and install packages to and from the public npm registry, you must install Node.js and the npm command line interface using either a Node version manager or a Node installer. We strongly recommend using a Node version manager to install Node.js and npm. We do not recommend using a Node installer, since the Node installation process installs npm in a directory with local permissions and can cause permissions errors when you run npm packages globally.
+To publish and install packages to and from the public npm registry, you +must install Node.js and the npm command line interface using either a Node +version manager or a Node installer. We strongly recommend using a Node +version manager to install Node.js and npm. We do not recommend using a +Node installer, since the Node installation process installs npm in a +directory with local permissions and can cause permissions errors when you +run npm packages globally.
To see if you already have Node.js and npm installed and check the installed version, run the following commands:
+To see if you already have Node.js and npm installed and check the +installed version, run the following commands:
node -v
npm -v
Node version managers allow you to install and switch between multiple versions of Node.js and npm on your system so you can test your applications on multiple versions of npm to ensure they work for users on different versions.
+Node version managers allow you to install and switch between multiple +versions of Node.js and npm on your system so you can test your +applications on multiple versions of npm to ensure they work for users on +different versions.
If you are unable to use a Node version manager, you can use a Node installer to install both Node.js and npm on your system.
+If you are unable to use a Node version manager, you can use a Node +installer to install both Node.js and npm on your system.
If you’re using OS X or Windows, use one of the installers from the Node.js download page. Be sure to install the version labeled LTS. Other versions have not yet been tested with npm.
+If you’re using OS X or Windows, use one of the installers from the +Node.js download page. Be sure to +install the version labeled LTS. Other versions have not yet been +tested with npm.
If you’re using Linux or another operating system, use one of the following installers:
+If you’re using Linux or another operating system, use one of the following +installers:
Or see this page to install npm for Linux in the way many Linux developers prefer.
+Or see this page to +install npm for Linux in the way many Linux developers prefer.
For more information on installing Node.js on a variety of operating systems, see this page.
+For more information on installing Node.js on a variety of operating +systems, see this page.