-
Notifications
You must be signed in to change notification settings - Fork 103
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
make type definitons "module": "nodenext"
compatible
#311
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment on fastify/fastify-cookie#184 (review)
Any progress on this one? |
…to nodenext-export
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening a PR! Can you please add a unit test?
added tests from fastify-cookie, should be g2g |
Could you rebase on top of master? |
…to nodenext-export
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@climba03003 @RafaelGSS PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I do not like to use namespace
.
The types here works just fine and support more area.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I concur with avoiding namespaces, though.
Well Typescript rewrite with esm support might be good point for future, currently idk if there's a better way to pass current test suite |
Checklist
npm run test
andnpm run benchmark
and the Code of conduct