-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Convert codebase to babel #670
Comments
I had started a while back on this. I was using decaffeinate. Worked well for fontkit. |
@devongovett Thanks for giving the pointers. Will try this weekend to convert the repository to use babel instead of coffee script. |
pls no babel... I use successfully Pdfkit for years on a NodeJs Server. Don't need another layer. If so I would prefer Typescript... |
@GoNode5 I don't see what would be a problem for the end user if we use babel? It just compiles down to be compatible with lower versions of node, and if there is no transpile step needed anymore we could just plug out the babel convert step. If we would use something like typescript we would always need a compile step. You as an end-user can just use the library as you did before, there will be no changes because of it in the API. |
Never worked or need for Babel. Frontend Angular, no React so that's my bias for Typescript. Javascript will stay forever. Babel / Typescript (like Coffeescript) will (should..) be obsolete on some point in time. Think E6 made huge progress. I don't see myself as an end-user... |
Closing for #707. |
Co-creator of
react-pdf
here again.As we discussed in #24, it would be beneficial to both of us if we convert the codebase to babel.
Can we already start with it? Or what is a good strategy to do so?
Happy if we can help.
The text was updated successfully, but these errors were encountered: