You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From a quick test, the node: prefix in imports is handled properly as long as ESLint in runned by Node 14 or newer. This also includes ESLint extension in VS Code which by defaults runs under Node 12 and will report an error.
The workaround for now (until VS Code upgrades Node) is to customize runtime option of ESLint extension:
{
"eslint.runtime": "node"// will use default node, make sure it's Node 14 or newer
}
Describe the feature
Make sure the config doesn't choke on
import * as fs from 'node:fs'
and alike.The text was updated successfully, but these errors were encountered: