Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node 16.x deprecations and problems. #478

Open
kaladay opened this issue Nov 4, 2021 · 2 comments
Open

Node 16.x deprecations and problems. #478

kaladay opened this issue Nov 4, 2021 · 2 comments

Comments

@kaladay
Copy link
Contributor

kaladay commented Nov 4, 2021

I've recently upgraded my node to a 16.x version and I now get this warning.

(node:5029) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead

Check if fs.rm(path, { recursive: true }) can be used on older versions of node as well to ensure compatibility.
If it is possible to make this change without breaking not too old releases (node 14.x and node 12.x), then it may be worth making this change.

(node:7704) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at weaver-components/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".

Installing to local npm (Verdaccio) errors with:

npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in.
npm ERR! need auth You need to authorize this machine using `npm adduser`
@kaladay kaladay changed the title Deprecation: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed Node 16.x deprecations. Nov 4, 2021
@kaladay kaladay changed the title Node 16.x deprecations. Node 16.x deprecations and problems. Nov 4, 2021
@kaladay
Copy link
Contributor Author

kaladay commented Sep 1, 2022

This might be resolved with this PR:

I think this should be reviewed to see if it is solved or not, so I am moving this into needs review.

@kaladay kaladay self-assigned this Sep 1, 2022
@kaladay
Copy link
Contributor Author

kaladay commented Sep 7, 2022

Still happens, despite the changes in the above referenced PR.

@kaladay kaladay removed their assignment Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant