forked from node-apn/node-apn
-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Modernize code (use typescript, use class syntax instead of prototype) #68
Labels
Comments
Yes. I think that it makes sense and I'd be glad to review a PR. |
Thanks for opening this issue!
|
Added a bounty so hopefully someone will pick this up. |
is this still valid? |
@mrevanzak yes, the issue is still up for grabs |
I would give it a try if it still $100 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A switch to typescript may make sense in a major version
index.d.ts may get out of sync with the implementation. It may be easier to write everything in typescript and add a publish hook to convert code to typescript
(https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-dynamodb/package.json https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#including-declarations-in-your-npm-package https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-dynamodb/tsconfig.json)
(the publish hook would trigger a typescript build to dist/ or a subdirectory)
Alternately, with --checkJs, jsdoc can be type checked in CI
Also, class syntax can be used in node 6+ - the upstream code was supporting node 4+ and declared
function Client
instead ofclass Client
https://github.com/parse-community/node-apn/blob/master/lib/client.jsWhat are the maintainer's thoughts on those ideas? Would you accept PRs?
The text was updated successfully, but these errors were encountered: