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

meta: update to babel 7 #9

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

meta: update to babel 7 #9

wants to merge 3 commits into from

Conversation

WikiRik
Copy link
Member

@WikiRik WikiRik commented Nov 20, 2022

This should not change any functionality, but I haven't tested the built code on the browser or with a low Node version. Therefore it's still in draft.

This brings us to the question of supported versions. The original has browser support and test on Node 10, although I think it has support for versions below that. What versions do we want to support? Just go with Node ^14.17.0 || >=16.0.0 like for sequelize or do we want to keep the support for browser/old Node versions? With babel this should not be too difficult I think, but we'll have to add CI for it. @ephys any preference?

@WikiRik WikiRik requested a review from ephys January 20, 2023 14:17
@ephys
Copy link
Member

ephys commented Jan 20, 2023

Do you think it's worth it to use babel VS rewriting in TS and using TSC?

@WikiRik
Copy link
Member Author

WikiRik commented Jan 20, 2023

I just used babel since it was already using that but using tsc should also be fine. I think however that the question does remain; do we want to keep supporting old browsers and old Node versions or keep the same version support as sequelize v7?

@ephys
Copy link
Member

ephys commented Jan 20, 2023

The same as sequelize, we don't need to support dead versions of node (and it should be fine for browsers, users always have the option to transpile the library if they need to support old browsers)

@WikiRik
Copy link
Member Author

WikiRik commented Jan 20, 2023

Then I'll use tsc in this project as well. New PR for that will follow soonish

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