[WIP] Upgrade to Eleventy 3 #71
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Seems like Eleventy 3 doesn't support the prior syntax due to promise gubbins? I dunno, I don't actually get it, but doing non-dynamic imports works. 11ty/eleventy#3286
|
This has fallen behind main quite significantly, so rather than go through rebase hell I'm just going to close it off and start the migration anew. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the website to Eleventy 3's pre-releases, in preparation for the new major release. As part of this, convert the Eleventy configuration and build scripts to use ESM format, as that now has first-party support.
Closes #35.