Eleventy: getPreviousCollectionItem missing from 0.11.0-beta.3

[ithinkihaveacat]

In 0.11.0-beta.2, filter functions like getPreviousCollectionItem() are available to JavaScript templates. In 0.11.0-beta.3, they are not.

That is, the following JavaScript template prints DEFINED in beta.2, and NOT DEFINED in beta.3:

module.exports = function (context) {
  console.log(this.getPreviousCollectionItem ? "DEFINED" : "NOT DEFINED");
};

I believe this is caused by https://github.com/11ty/eleventy/commit/9de36e8fcf9bbedf6199a8f82f12a7e9ca37a62e.

[Ryuno-Ki]

Oh, wait, there are new beta versions out already? :O

[zachleat]

Dang, sorry about this—I’ll get it patched up. I probably should start an alpha or daily npm tag to fit better with the increased project velocity

[pdehaan]

I like the npm @alpha tag idea, but I believe you can also install the latest from GitHub using npm i github:11ty/eleventy -D if one should ever need the latest cutting edge commit.

[zachleat]

Unfortunately it does not look like Netlify works with GitHub installs like that, at least the last time I tested it

[TigersWay]

With package.json like this one, it sure does deploy on netlify

...
  },
  "dependencies": {
    "@11ty/eleventy": "github:11ty/eleventy#master",
    "@fullhuman/postcss-purgecss": "^2.1.0",
...

[zachleat]

Beautiful, thank you @TigersWay

[zachleat]

This will ship with beta 4. Hopefully the last beta but we may do 5

[Ryuno-Ki]

Just learned about how to learn about new beta versions:

npm view @11ty/eleventy

Thanks @KyleMit!

[pdehaan]

You can also use npm info @11ty/eleventy dist-tags --json

{
  "latest": "0.10.0",
  "beta": "0.11.0-beta.3"
}