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

Dependency update #33

Open
aberaud opened this issue Dec 6, 2022 · 3 comments
Open

Dependency update #33

aberaud opened this issue Dec 6, 2022 · 3 comments

Comments

@aberaud
Copy link

aberaud commented Dec 6, 2022

Hi!

It would be awesome if the project was updated for Babel 7 :)
Many thanks

@typhonrt
Copy link
Member

typhonrt commented Dec 7, 2022

Hi @aberaud. Thanks for the reminder as the current arrangement is a bit long in the tooth. I have a lot of experience w/ modern ESM & Node packages, so quite likely I'll rework this package as straight ESM w/ no Babel / CJS build; Node 12+ at that point. Quite possibly I'll create a new mono-repo and build process instead of the many-repo arrangement currently.

As far as continuing to work on improving the analysis unfortunately I can't really justify the development cost being open source with no sponsors for this effort and it is not a project that I am actively using at least at this time. Hopefully arranging things as ESM and in a mono-repo format will make it easier to coordinate with anyone brave / has time enough to continue working on the metrics side of things.

Hopefully I can schedule the ESM conversion / repo maintenance aspects in the first quarter of next year.

@aberaud
Copy link
Author

aberaud commented Dec 7, 2022

That would be even better. I thought babel was used for code parsing/analysis, not just for packaging.

@typhonrt
Copy link
Member

typhonrt commented Dec 7, 2022

Oh it is... I'll switch to @babel/parser which is the new AST parser as well; oomph I'm not looking forward to debugging any potential AST changes. It has been a minute since I have examined this project. I did a minor bump ~3 years ago to the build process. I think I removed the dependence on babel-runtime at that time as that will cause issues for folks using a more recent version of Babel, so perhaps that sticking point is what I'm vaguely recalling as an issue when the Babel version is older. Nonetheless switching to a native ESM approach for the package will be best.

I'm expecting this to take ~1-2 weeks of effort, but hopefully it goes smoother.

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

No branches or pull requests

2 participants