-
Notifications
You must be signed in to change notification settings - Fork 132
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 #134
Comments
In case it's helpful, here's another popular library fixing the same issue. It looks like the first try didn't work; so this is something that would need to be tested with multiple versions of node. |
Any update on this? |
To get the ball rolling, I've created a pull request based on the mentioned postcss solution. Tested with node |
Thanks @ericgopak, really appreciated. |
upgrading nodejs to v15.8.0 fixed the warnings for me |
@omostan this works indeed, thanks for your reply! |
This could be closed (though I'm not sure whether it should be), since the deprecation in node was reversed:
If there were a benefit to the changes aside from eliminating the warning, it might be worth keeping this open, but I'm not sure what those benefits are. Comments on nodejs/node#36859 indicate that this deprecation may come back, but they've reversed the deprecation warnings for libs within |
In NodeJs 16 this issue reintroduced: Versions: 16.0.0 and 16.2.0 Any news? |
+1 |
1 similar comment
+1 |
Yep, can replicate this with v16.3.0 |
+1
|
I am getting the same warning:
Can someone please tell me how to fix this? |
same warning for now , i disabled the warnings by using cross-env: |
Same |
this is a ticking time bomb going for years. Some day it will go off and break production for sure ! |
I have exactly the same now on node |
Same! |
Same error :/ |
same error node version v16.10.0 |
1 similar comment
same error node version v16.10.0 |
Having the same issue with node v14.15.1 |
|
I am still facing this issue, almost a year later. I'm on v16.12.0, and there is a PR for this, as many people have already pointed out: #135 by @JonSenpai The CI fails for it, however; the v14.x job fails, to be specific. But maybe @ExE-Boss's suggestion could fix that? |
Yes, especially given the issues this causes with |
Potentially perhaps changing the export path to However, as per the nodejs documentation doing so would:
So the issues with this approach:
Another library postcss had the same issue (postcss gh-1561) and they solved it by being explicit about the exports. So if we would explicitly define the exports that are necessary rather than |
@prescience-data What are the issues that are caused in that library? |
v16.11.1 same |
Suggested a possible solution in this PR: #163 |
node |
+1 seems like this is broken |
node 16.14.0 same |
Hopefully fixed in #135, though they need to also cut a release. |
c'mon Microsoft wtf |
any news? |
@haggholm Doesn't seem like they'll cut a release anytime soon. Last release was in August. |
Umm... I made this error go away by changing in the ` ` swap out Why and how? I do not know. We can leave that to the tslib-overlords on whether this is acceptable or not. This works with I went through the [https://github.com/postcss/postcss/issues/1455](postcss issue) November 6 2020 Sheng Hong Fei comment. |
Bumping |
I had |
Are you sure this is correct? |
I'm sure - it is for a Vue.js application, so TS doesn't run at runtime; it's compiled JS when the app's runtime occurs. |
This has been fixed as of tslib 2.4.0. |
Hi tslib maintainers. It seems like this issue is back: |
I would think not, the package has both |
When building with tslib, I'm seeing the following on every build:
I'm pretty sure this started when upgrading to Node 15.1.0.
Environment:
This is an Angular project - I can provide a repro case if it's not obvious.
The text was updated successfully, but these errors were encountered: