-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
incompatible issue: Node 14 unsupported warning #1797
Comments
This fixes winstonjs#1797 issue
Cause it seems like it's not going to be fixed/merged anytime soon and I really don't want to migrate to winston@3, I've created forked npm package - https://www.npmjs.com/package/winston24. This is just [email protected] with fix for this warning applied and bumped to version 2.4.5. Published from this branch: https://github.com/rysenko/winston/commits/2.x |
Fixed via #1800 and a 2.4.5 release should be cut shortly. Thanks. Consider upgrading to winston 3 which is maintained and tested against the latest Node versions. |
Update webapp babel (via manual lockfile deletion & reinstall) due to babel/babel#11216 Update webapp node-sass for Node 14 support Update webapp element-ui due to ElemeFE/element#19389 Update graphql bcrypt to hopefully fix rebuild-on-node-version-change behavior Update graphql knex/pg to fix knex/knex#3836 Update graphql winston to fix winstonjs/winston#1797 Update graphql ts-node-dev to fix wclr/ts-node-dev#143 Pin version of graphql graphql-binding because I remember newer versions not being compatible Remove hacks needed for node 8 (asyncIterator polyfill, incorrect date format in ElapsedTime.spec.ts) Updated FilterPanel snapshot. It seems the reason it was reordered was because Array.prototype.sort started using a stable sorting algorithm in Node 11, and `sortFilterKeys` in store/mutations.js sorts against the same value for most items.
* Upgrade node to v14 Update webapp babel (via manual lockfile deletion & reinstall) due to babel/babel#11216 Update webapp node-sass for Node 14 support Update webapp element-ui due to ElemeFE/element#19389 Update graphql bcrypt to hopefully fix rebuild-on-node-version-change behavior Update graphql knex/pg to fix knex/knex#3836 Update graphql winston to fix winstonjs/winston#1797 Update graphql ts-node-dev to fix wclr/ts-node-dev#143 Pin version of graphql graphql-binding because I remember newer versions not being compatible Remove hacks needed for node 8 (asyncIterator polyfill, incorrect date format in ElapsedTime.spec.ts) Updated FilterPanel snapshot. It seems the reason it was reordered was because Array.prototype.sort started using a stable sorting algorithm in Node 11, and `sortFilterKeys` in store/mutations.js sorts against the same value for most items. * Re-enable supervisorctl autorestart * Debug logging about node versions * Ansible fixes * Fix use of nvm in Ansible/Supervisor * Update CircleCI image for Node 14 * Update graphql lockfile * Update suggested fix for missing DB schema during provision * Re-disable sm-cluster-autostart-daemon autorestart * Make "sm_activate_nvm" variable to simplify nvm use * Fix after merge
I'm still facing this issue, ive updated to @2.4.5 in my node modules and reinstalled, it still crashes but with no warning this time |
The old version was causing trouble: winstonjs/winston#1797 > Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency https://github.com/winstonjs/winston/blob/master/UPGRADE-3.0.md
The old version was causing trouble: winstonjs/winston#1797 > Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency https://github.com/winstonjs/winston/blob/master/UPGRADE-3.0.md
Please tell us about your environment:
winston
version?winston@3
winston@2
node -v
outputs:Ubuntu 18.04(wsl 1)
What is the problem?
while start program, have a warning showed.
i.
node --trace-warnings core.js
ii. show the blow
What do you expect to happen instead?
with no warning
Other information
The text was updated successfully, but these errors were encountered: