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

Upgrade to Node 18/19, also upgrade Astro if possible #119

Closed
Southpaw1496 opened this issue Mar 12, 2023 · 3 comments · Fixed by #243
Closed

Upgrade to Node 18/19, also upgrade Astro if possible #119

Southpaw1496 opened this issue Mar 12, 2023 · 3 comments · Fixed by #243
Assignees
Labels
enhancement New feature or request

Comments

@Southpaw1496
Copy link
Contributor

Thanks to #115, we can now use modern Node versions without Cloudflare having a heart attack, so we should upgrade. 18 is the LTS version, but I see no reason why we shouldn't upgrade to 19 if we can.

We should also upgrade to Astro 2.x if our extensions support it.

@Southpaw1496 Southpaw1496 added the enhancement New feature or request label Mar 12, 2023
@pluiedev
Copy link
Contributor

Upgrading Node is easy but if we were to upgrade to Astro 2.x, I'd like to make use of content collections since they provide a much better way to view and organize pages, which would cut down on a lot of wacky uses of Astro.glob in the codebase. However it looks quite complex and I don't really have spoons for that, but if anyone wants to tackle that then go ahead 💜

@Southpaw1496
Copy link
Contributor Author

Is there any reason not to upgrade to Node 19?

@pluiedev
Copy link
Contributor

Is there any reason not to upgrade to Node 19?

Can't think of any

@Southpaw1496 Southpaw1496 assigned Southpaw1496 and unassigned pluiedev and obj-obj Mar 13, 2023
@Southpaw1496 Southpaw1496 linked a pull request Aug 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants