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

Suggestion: Investigate upgrading to Eleventy v3.0.0 #644

Closed
1 task
nzakas opened this issue Oct 2, 2024 · 2 comments · Fixed by #690
Closed
1 task

Suggestion: Investigate upgrading to Eleventy v3.0.0 #644

nzakas opened this issue Oct 2, 2024 · 2 comments · Fixed by #690
Assignees
Labels
accepted enhancement New feature or request

Comments

@nzakas
Copy link
Member

nzakas commented Oct 2, 2024

What problem do you want to solve?

We are still using Eleventy v2.x, which can be fairly slow when regenerating the site.

What do you think is the correct solution?

Eleventy v3.0.0 was just released. We should investigate upgrading to see if it improves performance (any other issues):
https://github.com/11ty/eleventy/releases/tag/v3.0.0

Participation

  • I am willing to submit a pull request for this change.

Additional comments

No response

@nzakas nzakas added the enhancement New feature or request label Oct 2, 2024
@github-project-automation github-project-automation bot moved this to Needs Triage in Triage Oct 2, 2024
@amareshsm
Copy link
Member

I will look into this.

@amareshsm amareshsm self-assigned this Oct 3, 2024
@amareshsm amareshsm moved this from Needs Triage to Ready to Implement in Triage Oct 3, 2024
@nzakas
Copy link
Member Author

nzakas commented Jan 29, 2025

@amareshsm are you still planning on working on this?

@github-project-automation github-project-automation bot moved this from Ready to Implement to Complete in Triage Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted enhancement New feature or request
Projects
Status: Complete
Development

Successfully merging a pull request may close this issue.

2 participants