import 8.41.0 source

[pve-eslint.git] / eslint / docs / src / rules / no-sync.md

diff --git a/eslint/docs/src/rules/no-sync.md b/eslint/docs/src/rules/no-sync.md
index 4b5eb5768101185007c40ee8655e337de2554114..254974411e43425a44c8a20e0732fffbfc37cf61 100644 (file)
--- a/eslint/docs/src/rules/no-sync.md
+++ b/eslint/docs/src/rules/no-sync.md
@@ -1,11 +1,10 @@
 ---
 title: no-sync
-layout: doc
 rule_type: suggestion
 ---
 
 
-This rule was **deprecated** in ESLint v7.0.0. Please use the corresponding rule in [`eslint-plugin-node`](https://github.com/mysticatea/eslint-plugin-node).
+This rule was **deprecated** in ESLint v7.0.0. Please use the corresponding rule in [`eslint-plugin-n`](https://github.com/eslint-community/eslint-plugin-n).
 
 In Node.js, most I/O is done through asynchronous methods. However, there are often synchronous versions of the asynchronous methods. For example, `fs.exists()` and `fs.existsSync()`. In some contexts, using synchronous operations is okay (if, as with ESLint, you are writing a command line utility). However, in other contexts the use of synchronous operations is considered a bad practice that should be avoided. For example, if you are running a high-travel web server on Node.js, you should consider carefully if you want to allow any synchronous operations that could lock up the server.