Alessandro Commodari
Alessandro Commodari
Hmmm maybe I jumped the gun with this PR... Honestly whether to include `@types` in dependencies or devDependencies as a _library_ is not a straightforward decision... I myself don't have...
As of writing this there is now a version 9 of `uuid` as well
Hey 👋 I am currently using `[email protected]` and I have also encountered this issue when migrating to node 18. I see there have been PRs done to try and resolve...
Any updates on this? i also noticed that the types on `@types/shippo` are not great and created a discussion [here](https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/67776) but not sure if those types are even being maintained...
As someone who's also trying to migrate to the new config format and uses this plugin it would be great to get support on this.
I believe these are the Typescript docs in question? https://www.typescriptlang.org/docs/handbook/esm-node.html
Removing `const { emitWarning } = require('node:process');` completely will not only fix the github action error in #1929 but also resolve this issue making `restify` truely support >14.0.0
Will we publish a new version to npm once this PR is merged? trying to figure out an eta for the package upgrade 😄
Another thing to note about this PR @dcavanagh , if you are adding github ci should we not remove travis? or is the goal to have both?
@notaphplover any new blogs in the works or up to date roadmaps we can follow along with? would be great to have a sense of how close we are to...