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

chore(deps)!: upgrade consola to v3 and minimum node version #128

Merged
merged 3 commits into from
Nov 17, 2023

Conversation

rchl
Copy link
Contributor

@rchl rchl commented Nov 16, 2023

πŸ”— Linked issue

nuxt/nuxt#24343

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme, or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Addressing the nuxt/nuxt#24343 issue which is about outdated consola being used in a couple of Nuxt 2 packages.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@rchl
Copy link
Contributor Author

rchl commented Nov 17, 2023

Bumped node in CI to 16. Maybe it will fix it.

The package specifies 12.22.12 as minimum version in package.json which is unreasonable these days anyway but I have not bumped that to avoid breaking changes (I'm assuming that since the code is built, it might still work with node 12.x)

@pi0 pi0 changed the title fix: bump consola to 3.x to align with other nuxt 2 packages feat: upgrade consola to v3 and minimum node version Nov 17, 2023
@pi0 pi0 changed the title feat: upgrade consola to v3 and minimum node version feat!: upgrade consola to v3 and minimum node version Nov 17, 2023
@pi0 pi0 changed the title feat!: upgrade consola to v3 and minimum node version chore(deps)!: upgrade consola to v3 and minimum node version Nov 17, 2023
@@ -50,6 +50,6 @@
"webpack": "3 || 4 || 5"
},
"engines": {
"node": ">=v12.22.12"
"node": ">=14.18.0"
Copy link
Member

Choose a reason for hiding this comment

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

(we might upgrade to higher version in next major, will have to check other deps)

@@ -1,5 +1,5 @@
import { consola } from '../utils/cli'
import { Reporter } from 'src/types'
import { Reporter } from '../types'
Copy link
Member

Choose a reason for hiding this comment

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

Was this change necessary?

Copy link
Contributor Author

@rchl rchl Nov 17, 2023

Choose a reason for hiding this comment

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

Caused error in the editor:

Screenshot 2023-11-17 at 11 40 45

If you insist then I can look into fixing that differently (probably a missing mapping or baseDir in tsconfig) but I thought it's better to be consistent and use paths relative to the current file anyway.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also this change doesn't affect compiled bundle, as far as I can tell, so IMO keeping this change is better.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah it is better (hate old me that didn't used relative haha) only preferred that if it was not part of this commit but also okay πŸ‘πŸΌ

@pi0 pi0 merged commit 7834861 into unjs:main Nov 17, 2023
@pi0
Copy link
Member

pi0 commented Nov 17, 2023

@rchl I might need to delay this release to next week as have some priorities. If it is a blocker for something, please mention. (and thanks for PR)

@rchl rchl deleted the fix/consola branch November 17, 2023 10:50
@rchl
Copy link
Contributor Author

rchl commented Nov 17, 2023

No, not a blocker. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants