Skip to content

Commit

Permalink
Fix linting errors
Browse files Browse the repository at this point in the history
  • Loading branch information
nzakas committed Feb 1, 2024
1 parent afc9c23 commit e5f793e
Show file tree
Hide file tree
Showing 4 changed files with 5 additions and 4 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ jobs:
- name: Install Node.js
uses: actions/setup-node@v3
with:
node-version: 16
node-version: lts/*
- name: Install Packages
run: npm install
env:
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ npm install --save-dev eslint eslint-plugin-markdown
In your `eslint.config.js` file, import `eslint-plugin-markdown` and included the recommended config to enable the Markdown processor on all `.md` files:

```js
// / eslint.config.js
// eslint.config.js
import markdown from "eslint-plugin-markdown";

export default [
Expand Down
3 changes: 2 additions & 1 deletion eslint.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,8 @@ module.exports = [
}
},
rules: {
"lines-around-comment": "off"
"lines-around-comment": "off",
"n/no-missing-import": "off"
}
}
];
2 changes: 1 addition & 1 deletion tests/lib/plugin.js
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ describe("LegacyESLint", () => {
// the plugin, so we need to make sure it's resolvable and link it
// if not.


// eslint-disable-next-line n/no-missing-require -- Known possible failure.
require.resolve("eslint-plugin-markdown");
} catch (error) {
if (error.code === "MODULE_NOT_FOUND") {
Expand Down

0 comments on commit e5f793e

Please sign in to comment.