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

DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at PATH_TO_PROJECT/node_modules/vuex/package.json. #2071

Closed
MadeInTomorrow opened this issue Oct 13, 2021 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@MadeInTomorrow
Copy link

MadeInTomorrow commented Oct 13, 2021

Version

4.0.2

Reproduction link

github.com
I used a PR that solved the same exact issue in postcss.

Steps to reproduce

Environments:
node v16.11.1
npm v8.0.0
@vue/cli 4.5.13

Vue 3 project (v3.2.20)

Steps:

  1. Run "vue ui"

What is expected?

No warnings

What is actually happening?

This warning:

(node:19450) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at PATH_TO_PROJECT/node_modules/vuex/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use node --trace-deprecation ... to show where the warning was created)


This is likely caused by new deprecation warnings introduced in node 16.

It was already fixed in postcss by updating the deprecated folder mapping to use a subpath pattern.
See this PR:
postcss/postcss@93359b7

All they did was replace this line
"./": "./"

with this
"./": "./"

@kiaking
Copy link
Member

kiaking commented Oct 14, 2021

This is already fixed by #2048. We just need to release a new version. Please wait just a bit more 🙏

@kiaking kiaking closed this as completed Oct 14, 2021
@MadeInTomorrow
Copy link
Author

Thank you!
Sorry for the duplicate, I'll make sure to search the closed issues too next time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants