Skip to content

Commit

Permalink
Try to avoid Node.js 15 warning
Browse files Browse the repository at this point in the history
  • Loading branch information
@ai
ai committed Nov 10, 2020
1 parent 9958714 commit 92155c7
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions package.json
View file
Expand Up @@ -11,6 +11,7 @@
"import": "./lib/postcss.mjs",
"types": "./lib/postcss.d.ts"
},
"./*": "./*",
"./": "./"
},
"main": "./lib/postcss.js",
Expand Down

14 comments on commit 92155c7

@rafiksamman1982
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bug is back in node 15.2.1

@ai
Copy link
Member Author

@ai ai commented on 92155c7 Nov 16, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rafiksamman1982 put a way to reproduce the warning to #1455

@za0888
Copy link

@za0888 za0888 commented on 92155c7 Nov 24, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"build": "postcss ./src -o ./dist"

@ai
Copy link
Member Author

@ai ai commented on 92155c7 Nov 24, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@za0888 can you create a repository on GitHub to reproduce the warning?

@omostan
Copy link

@omostan omostan commented on 92155c7 Feb 5, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

upgrading nodejs to v15.8.0 fixed the warnings for me

@AndiKod
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have that warning for the first time, after upgrading to node v16.0.0 and npm v7.10.0
Use of deprecated folder mapping "./" in the "exports" field ... node_modules\postcss\package.json.

@ronaksinghbagga
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am facing same issue in node v16.2.0 & npm 7.13.0

@jojudre
Copy link

@jojudre jojudre commented on 92155c7 Sep 2, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the same

@naimurcse
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am facing the same issue in node v16.9.0 & npm 7.21.1. Plz help

@OlegRashchinskiy
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same problem in node v16.16.1 and npm 7.20.3

@naydenova-onedot
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have the same problem in node v16.13.0

@rodolformartins
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i have the same problem in node v16.14.1 using wsl.

@jerrywebman
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have the same problem in node v16.13.0

same here. Still experiencing the same issue with node v16.13.0. any fix yet?

@Michael-Gatmaitan
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also have the same problem, I'm using node v16.17.1, is there any fixes available?

Please sign in to comment.