lint squiggles do not appear in vscode with remark extension installed

[LokiMidgard]

I installed remark extension to vscode and the formatting works, but warnings are not displayed (not in the problem window, nor in the editor)

I added following package.json

{
  "name": "sand-artefakte",
  "version": "1.0.0",
  "description": "",
  "scripts": {
    "format": "remark . --output"
  },
  "author": "",
  "license": "ISC",
  "remarkConfig": {
    "plugins": [
      "remark-preset-lint-consistent",
      "remark-preset-lint-recommended",
      "remark-preset-lint-markdown-style-guide",
      "remark-frontmatter",
      "remark-lint"
    ], 
    "settings": {
      "bullet": "-"
    }
  },
  "dependencies": {
    "remark": "^15.0.1",
    "remark-cli": "^12.0.1",
    "remark-frontmatter": "^5.0.0",
    "remark-lint": "^10.0.0",
    "remark-lint-maximum-line-length": "^4.0.1",
    "remark-preset-lint-consistent": "^6.0.0",
    "remark-preset-lint-markdown-style-guide": "^6.0.0",
    "remark-preset-lint-recommended": "^7.0.0",
    "remark-toc": "^9.0.0"
  }
}

executing npm run format outputs

…
12:1          warning Unexpected unordered list marker `*`, expected `-`
          unordered-list-marker-style   remark-lint
13:1          warning Unexpected unordered list marker `*`, expected `-`
          unordered-list-marker-style   remark-lint
…

however the editor shows nothing:

[remcohaszing]

I am seeing diagnostics with the code that you provided.

You dependencies are up-to-date, so that’s good. What version of VSCode and the remark extension are you using? And what operating system?

[remcohaszing]

Those versions all look good. Windows support can be tricky sometimes, but it should work. Do you use WSL by any chance?

[LokiMidgard]

I noticed that when I create another file in the project, it actually worked.

I tried to find out what Part of the original file was responsable for the error. And the result was this:
outline.md

• Removing any line from this will trigger the display of errors
• If you add something again, it will still show errors, only after a reload of VSCode errors disapear again
• I started with a file with more text and removing the quote block triggerd it earlier then removing other blocks
• Also removing long lines seem to trigger it earlier

It could be a memory problem, so the file may not reproduce this behavior on another system…

[LokiMidgard]

Those versions all look good. Windows support can be tricky sometimes, but it should work. Do you use WSL by any chance?

No, I used it in the past, but have disabled it now (not sure if it was ever enabled on this Laptop)

[remcohaszing]

I managed to reproduce it by running the following script in the vscode-remark repo.

import {PassThrough} from 'node:stream'
import {engine} from 'unified-engine'
import {VFile} from 'vfile'
import {remark} from 'remark'

const lorem =
  'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. No dicam aperiam vis. An dicant apeirian qui, at vide indoctum pro. Offendit eleifend moderatius ex vix, quem odio mazim et qui, purto expetendis cotidieque quo cu, veri persius vituperata ei nec. Pri posse graeco definitiones cu, id eam populo quaestio adipiscing, usu quod malorum te. Et clita interesset quo. Scripta periculis ei eam, te pro movet reformidans. Offendit eleifend moderatius ex vix, quem odio mazim et qui, purto expetendis cotidieque quo cu, veri persius vituperata ei nec. Scripta periculis ei eam, te pro movet reformidans. Offendit eleifend moderatius ex vix, quem odio mazim et qui, purto expetendis cotidieque quo cu, veri persius vituperata ei nec. Offendit eleifend moderatius ex vix, quem odio mazim et qui, purto expetendis cotidieque quo cu, veri persius vituperata ei nec. Eos verear percipit ex, eos ne eligendi inimicus.\n'

const value = lorem.repeat(10)

await new Promise((resolve) => {
  engine(
    {
      files: [
        new VFile({
          value,
          path: new URL('example.md', import.meta.url)
        })
      ],
      packageField: 'remarkConfig',
      pluginPrefix: 'remark',
      processor: remark,
      streamError: new PassThrough(),
      streamOut: new PassThrough()
    },
    (errors, code, context) => {
      console.dir(errors)
      console.dir(code)
      console.dir(context)
      resolve(undefined)
    }
  )
})

When this script is run using Node.js 20.15.1 (the version bundled with VSCode) or 20.17.0 (latest in the 20.x release line), this yields exit code 13. Exit code 13 means a promise didn’t get resolved. If this is run using Node.js 22, it runs the console logging and exists succesfully.

I did some debugging, but I didn’t manage to find out what causes it.

[LokiMidgard]

Thank you for your help. I just updated Node.js :)

[remcohaszing]

Note that I’m explicitly talking about the Node.js version that comes with VSCode. You don’t control that. The problem will eventually go away with some VSCode update that updates to Node.js 22, but I have no clue when that would be.

Since this is an issue in unified-engine, caused by a regression in Node.js 20, perhaps @wooorm has an idea how to fix it.

[wooorm]

What is the problem?

[remcohaszing]

The callback given to unified-engine in the script above is never called when using Node.js 20. It works fine in Node.js 22.