unconfident

Setting front matter variable permalink: false results in a compilation error

4

This code leads to problems in some situations when permalink is customized by the user. https://github.com/adamduncan/eleventy-plugin-i18n/blob/e1053383eb179adc2f512dac8a3a698a8b509a7d/i18n.js#L20-L22 Here are couple of examples: **1. permalink changed to a file in top level...

Fixes #4 by parsing context locale from `page.filePathStem` instead of `page.url`. This should be considered a breaking change, especially because of regexp. ~~Also because filePathStem is used required minimum supported...

Unmaintained, messy and out of date. Can we fix this?

6

Here's a short recap of what's been going on: `babel-root-import` has ben unnamed to `babel-plugin-root-import` about a year ago. Since then readme and the code of this module has been...

Contents of the `package.json` imply that CircleCI is being used. This pull request forces newer version of Node.js to be used so tests wouldn't fail due to lack of ES6...

This is a follow up for #11. Most notable changes: - `.babelrc` has higher priority than `package.json` - Doesn't throw if `package.json` is missing - Top level directory correctly detected...

`babel-root-import` has ben unnamed to `babel-plugin-root-import` about a year ago. This pull request updates code, docs and description to use and refer to babel plugin under its new name and...

Invalid output produced

1

Having `font-variant` set to `initial` before `font-feature-settings` property somehow corrupts produced output for `font-feature-settings`. **Input:** ```css .this-will-be-broken { font-variant: initial; font-feature-settings: normal; } .this-will-not { font-variant: normal; font-feature-settings: normal; }...