Importing fs constants in node:fs/promises throws an error

[kapekost]

Affected URL(s)

https://nodejs.org/api/fs.html#fspromisesaccesspath-mode

Description of the problem

import { access, constants } from 'node:fs/promises';

the above constants seems to be badly exported. As a workaround one can import * from 'node/fs

[mscdex]

What is the error that is thrown?

[Trott]

It works fine for me in Node.js 18 and 19. What version are you using?

[Trott]

Works in Node.js 16 as well. It does not work in Node.js 14 but the documentation for 14.x doesn't include that, so it seems like all supported releases are working as expected.

[kapekost]

must be the version, I was under the impression I defaulted 19 just before that, but apparently I am still on 17..
something is not working ok with nvm use 19 command on windows :(
works ok with node v19 on a container

import { access, open, constants } from 'node:fs/promises';
                       ^^^^^^^^^
SyntaxError: The requested module 'node:fs/promises' does not provide an export named 'constants'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:127:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:191:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:331:24)
    at async loadESM (node:internal/process/esm_loader:88:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)

C:>node -v
v17.2.0

[Trott]

Yeah, 17.x doesn't work with this. 17.x is also no longer supported as of about 5 months ago. So, yeah, try updating to 18.x and it should work.

[Trott]

Pinging @nodejs/version-management in case anyone wants to offer suggestions or try to troubleshoot @kapekost's possible issue with nvm for Windows.

[coreybutler]

@kapekost - please see coreybutler/nvm-windows#708.

For anyone landing here from Google, NVM4W 1.1.8 and below requires the full version, i.e. nvm install 19.0.0. In NVM4W 1.1.9 and above, you can use nvm install latest, nvm install lts, etc. See the repo for details.

[kapekost]

Thanks! Looks lime the older NVM version on windows, was reporting a successful switch to nodejs 19, and it was digesting a permission error. It worked ok after upgrading that to latest, and run as admin