-
Notifications
You must be signed in to change notification settings - Fork 131
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
Deprecation warning in Node 16 #152
Comments
I just triggered this on a new build, it's confusing though:
|
My error message looks slightly different:
According to Node docs, it should just be replacing "exports": {
".": {
"module": "./tslib.es6.js",
"import": "./modules/index.js",
"default": "./tslib.js"
},
- "./": "./"
+ "./*: "./*"
} Though I can't see the reason to export everything in the root. Mostly since there are pretty much no Javascript files to import. The only thing that might need to be exported as far as I know is - "./": "./"
+ "./package.json: "./package.json" |
i have the same issue on a svelte project because of some deep dependency. Would be good to have this warning gone |
This is a duplicate of #134. Would be nice to see fixed |
tslib now breaks in node 17:
|
Dupe of #134, fixed back in tslib 2.4.0. |
When building my Angular 12 library application i'm getting a new deprecation warning after updating to Angular 12.
My warning message (local folders):
(node:9872) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at C:\g\LogicmediaAngularNpm\logicmedia-angular\library-container-project\projects\logicmedia-angular\node_modules\tslib\package.json.
Update this package.json to use a subpath pattern like "./".
I'm using [email protected] and Angular 12.1.1
I'm compiling my Angular library application using Ivy partial compilation mode.
🙁 Actual behavior
My library application builds and my npm package can be published but publishing with red lines is not intended.
🙂 Expected behavior
Angular not showing these red lines when building.
The text was updated successfully, but these errors were encountered: