DEV Community

Cover image for Migrating to Eleventy 2.0
Silvestar Bistrović
Silvestar Bistrović

Posted on • Originally published at silvestar.codes

Migrating to Eleventy 2.0

Last week I finally upgraded my Eleventy instance after using version 0.12.1 for over a year. I tried to do this earlier but always gave up because I stumbled upon this or that issue. This time was no different, but I was determined to resolve all problems.

Issues

The primary issue when updating to the new Eleventy was my templating language - Liquid. I chose Liquid because I am familiar with it since I work with Jekyll and Shopify every now and then.

The first issue that occurred was:

illegal filename "undefined" (via AssertionError)
Enter fullscreen mode Exit fullscreen mode

After a quick investigation, I decided to switch to my own instance of Liquid library, as documented on the Eleventy site.

I added the following code:

const { Liquid } = require("liquidjs");

module.exports = (eleventyConfig) => {
  let options = {
    extname: ".liquid",
    dynamicPartials: false,
    strictFilters: false,
    jsTruthy: true,
    root: ["site/_layouts"]
  };

  eleventyConfig.setLibrary("liquid", new Liquid(options));
}
Enter fullscreen mode Exit fullscreen mode

The most important part here is the dynamicPartials: false setting which resolves common pitfalls if you include partials without quotation marks.

Next issue was:

unexpected token at "{{ read.date ..." (via AssertionError)
Enter fullscreen mode Exit fullscreen mode

I was using a variable inside the assign statement in Liquid, like so:

{% assign readHref = {{ read.date }} | prepend: '#' %}
Enter fullscreen mode Exit fullscreen mode

All I had to do is to remove the curly brackets around the variable:

{% assign readHref = read.date | prepend: '#' %}
Enter fullscreen mode Exit fullscreen mode

The final issue I had was:

Failed to lookup "../../assets/dist/css/devcards.min.css" in "site/_layouts" (via Error)
Enter fullscreen mode Exit fullscreen mode

Apparently, Liquid can only look up files within the root folder defined in the configuration. The workaround was to define a new custom Liquid filter that returns the content of the file like so:

eleventyConfig.addLiquidFilter('getCritical', (critical) => {
  return fs.readFileSync(`./assets/dist/css/${critical}.critical.min.css`)
}
Enter fullscreen mode Exit fullscreen mode

And that's it. After resolving these issues, I could finally use the new version of the Eleventy static site generator.

For anyone interested, here's the full commit: https://github.com/maliMirkec/personal-website/commit/f18c059ead7abf166f99715261638ccf9944cf5f.

Top comments (3)

Collapse
 
ingosteinke profile image
Ingo Steinke, web developer

Adding your post to my reading list, as I gave up to migrate from 0.x to 1.0 and hope to jump to 2.0 some time this year.

Collapse
 
starbist profile image
Silvestar Bistrović

Good luck! \m/

Collapse
 
pozda profile image
Ivan Pozderac

Just updated yesterday, seems nunjucks wasn't really affected that much but on the other note I use just some simple stuff.

Thanks for keeping us posted and for sharing your solution!