tools: unpin eslint-plugin-markdown

[Trott]

First commit:

tools: remove pinning of eslint-plugin-markdown

An issue affecting Node.js source has been fixed in
eslint-plugin-markdown so we don't need to pin it to beta-4 anymore.

Refs: https://github.com/eslint/eslint-plugin-markdown/issues/69

Second commit:

tools: update eslint-plugin-markdown

Update eslint-plugin-markdown to beta-7. Other dependencies were updated
as well by the `update-eslint.sh` script.

/cc @vsemozhetbyt

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

Affected core subsystem(s)

tools

[Trott]

Hmmm, this seems to have only bumped it to beta-6 (because beta-7 hasn't been published to npm yet) but it doesn't seem to trigger any errors so ¯\(ツ)/¯

[vsemozhetbyt]

@Trott I was on it and had the same issue, but the npm install --no-bin-links --production [email protected] did the thing.

It seems we should have issues with doc linting after 1.0.0-beta.7 due to new skip comment format and no fall-through.

[Trott]

@Trott I was on it and had the same issue, but the npm install --no-bin-links --production [email protected] did the thing.

It seems we should have the issues with doc linting after 1.0.0-beta.7 due to new comment skip format and no fall-through.

Cool. Want me to close this and you can handle it whenever/however is best?

[vsemozhetbyt]

FWIW, should tools/package-lock.json be auto updated, manually updated or ignored?

https://github.com/Trott/io.js/blob/unpin-eslint-plugin-markdown/tools/package-lock.json#L196-L199

[vsemozhetbyt]

It seems the tools/eslint/package-lock.json is auto updated:

https://github.com/Trott/io.js/blob/unpin-eslint-plugin-markdown/tools/eslint/package-lock.json#L183-L186

[vsemozhetbyt]

I can try to handle this, but I cannot run update-eslint.sh on Windows. Would the npm install --no-bin-links --production [email protected] suffice for update commit?

[Trott]

Would the npm install --no-bin-links --production [email protected] suffice for update commit?

That along with two other steps:

• npm install -g dmn && dmn -f clean to remove a small number of unnecessary files.

• And update tools/update-eslint.sh to change @1.0.0-beta.4 to @next.

[vsemozhetbyt]

@Trott
PTAL: #14047

1. I've used the message of your first commit.
2. I've manually updated eslint-plugin-markdown part of tools/package-lock.json according to tools/eslint/package-lock.json, not sure if any other changes are required in this file.
3. Docs are fixed in the commit 3.

[Trott]

Closing in favor of #14047