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 Eleventy 3.0, transition JavaScript to ESM #82

Merged
merged 9 commits into from
Sep 30, 2024
Merged

Conversation

querkmachine
Copy link
Owner

Finishes what #71 started. Closes #35.

Changes

  • Updates the Eleventy dependency to the latest 3.0 canary release.
  • Sets the package type to "module" so that files are expected to be ESM format.
  • Updates all build, configuration and data related files from CommonJS to ESM format.

Additionally

  • Renames the configuration file from .eleventy.js to eleventy.config.js.
  • Changes the global paths.json file to ESM formatted JS and renames it paths.js for ease of use in ESM. assert/with declarations are still considered experimental by node.
  • Changes the about section's 11tydata file (about.json) to ESM formatted JS and renames it about.11tydata.js, for consistency with other 11tydata files.
  • Fixes a front matter parsing issue that hasn't been flagged before. Seemingly this is because of stricter checks on YAML formatting in Eleventy 3.0 or it's dependencies.

@querkmachine querkmachine self-assigned this Sep 30, 2024
@querkmachine querkmachine merged commit 209b585 into main Sep 30, 2024
@querkmachine querkmachine deleted the eleventy-3 branch September 30, 2024 21:13
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

Successfully merging this pull request may close these issues.

Transition config scripts to ESM format (Eleventy 3.0)
1 participant