Deprecation warning: Use of deprecated folder mapping "./" in the "exports" field
See original GitHub issueI just got the following warning:
(node:14084) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./"
in the "exports" field module resolution of the package at ...\node_modules\postcss\package.json.
Update this package.json to use a subpath pattern like "./*".
It looks like the deprecated mapping is still in use on the most recent version. I haven’t looked into it so I don’t know if this is really as simple as exchanging ./
for ./*
, just thought I’d let you know.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:16 (5 by maintainers)
Top Results From Across the Web
Issues - GitHub
DeprecationWarning : Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at G:\SNWS\sn-micro-front-web-project-template ...
Read more >Ask Question - Stack Overflow
DeprecationWarning : Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at node_modules\postcss\ ...
Read more >Deprecated APIs | Node.js v19.3.0 Documentation
Deprecated APIs#. Node.js APIs might be deprecated for any of the following reasons: Use of the API is unsafe. An improved alternative API...
Read more >App cannot be build - Questions about Thunkable - Community
Cannot resolve the path to “fsevents” package. (node:435007) [DEP0148] DeprecationWarning: Use of deprecated folder mapping “./” in the “exports ...
Read more >PostCSS on Twitter: "PostCSS 8.2.12 was released. We fixed ...
12 was released. We fixed DEP0148 deprecation warning from Node.js 16: “Use of deprecated folder mapping "./" in the "exports" field” ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Semigradsky Hi! This warning also ocurred wiith nodejs 16.0 (current lts).
@deadcoder0904 seems like you still using old PostCSS in Next.js dependencies.
Update nested dependencies with
npm update
oryarn upgrade
.