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

Update tooling #1132

Closed
manthey opened this issue Dec 22, 2021 · 1 comment · Fixed by #1141
Closed

Update tooling #1132

manthey opened this issue Dec 22, 2021 · 1 comment · Fixed by #1141
Labels

Comments

@manthey
Copy link
Contributor

manthey commented Dec 22, 2021

Many of the development packages used by GeoJS are stale. We should update them all to modern versions. For ease of development, we should abandon using PhantomJS -- it isn't maintained and both Chrome and Firefox have sensible headless versions for testing.

manthey added a commit that referenced this issue Dec 22, 2021
manthey added a commit that referenced this issue Dec 22, 2021
Note: hexo 6.0.0 was just released but doesn't work directly.  This
should be revisited in a few weeks and adjusted to work with hexo 6.

This is part of #1132.
manthey added a commit that referenced this issue Dec 22, 2021
This also removes PhantomJS as a test environment.

This is part of #1132.
manthey added a commit that referenced this issue Dec 22, 2021
manthey added a commit that referenced this issue Dec 22, 2021
manthey added a commit that referenced this issue Dec 22, 2021
Update js-yaml and typeface-lato packages as part of #1132.
manthey added a commit that referenced this issue Jan 3, 2022
manthey added a commit that referenced this issue Jan 4, 2022
This has many fewer stale npm packages (so many fewer warnings).  Tests
can use all of modern javascript.  This should be easier to maintain in
the future.

Note the built bundles are somewhat smaller due to modernization of some
packages.

This is part of and closes #1132.
manthey added a commit that referenced this issue Jan 4, 2022
This has many fewer stale npm packages (so many fewer warnings).  Tests
can use all of modern javascript.  This should be easier to maintain in
the future.

Note the built bundles are somewhat smaller due to modernization of some
packages.

This is part of and closes #1132.
manthey added a commit that referenced this issue Jan 4, 2022
This has many fewer stale npm packages (so many fewer warnings).  Tests
can use all of modern javascript.  This should be easier to maintain in
the future.

Note the built bundles are somewhat smaller due to modernization of some
packages.

This is part of and closes #1132.
@github-actions
Copy link

github-actions bot commented Jan 4, 2022

🎉 This issue has been resolved in version 1.6.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant