11ty upgrade helper log

eleventy-upgrade-help.log

[@11ty/eleventy-upgrade-help] ---
[@11ty/eleventy-upgrade-help] This plugin will help you migrate from 1.0 to 2.0.
[@11ty/eleventy-upgrade-help] If you are migrating from 0.x, downgrade to the 1.0 version of this plugin!
[@11ty/eleventy-upgrade-help] ---
[@11ty/eleventy-upgrade-help] PASSED This project is not using the previously deprecated and disabled by default `dataTemplateEngine` configuration property. Read more at https://www.11ty.dev/docs/data-preprocessing/
[@11ty/eleventy-upgrade-help] PASSED This project is not using the `--passthroughall` command line flag. Read more at https://www.11ty.dev/docs/copy/#passthrough-everything
[@11ty/eleventy-upgrade-help] NOTICE The `liquidjs` dependency was updated from 9.x to 10.x. This should not require action, but you can read the full release notes: https://github.com/harttle/liquidjs/releases/tag/v10.0.0
[@11ty/eleventy-upgrade-help] NOTICE Markdown’s indented code blocks have been disabled by default in 2.0. Unfortunately, this plugin does *NOT* currently test whether this change affects your content. You can re-enable this feature using `eleventyConfig.amendLibrary("md", mdLib => mdLib.enable("code"))`. Read more: https://www.11ty.dev/docs/languages/markdown/#indented-code-blocks
[@11ty/eleventy-upgrade-help] PASSED Eleventy has a new default ignore pattern of `**/node_modules/**` (previously: `node_modules/**`). Read more, including how to revert this behavior: https://www.11ty.dev/docs/ignores/#node_modules. This does not appear to affect your project, as you have no nested node_modules folders!
[@11ty/eleventy-upgrade-help] PASSED This project is using Node 14 or newer!
[@11ty/eleventy-upgrade-help] PASSED This project is not using the Render plugin. If it did, I’d remind you that the `renderTemplate` shortcode behavior changed slightly in 2.0. But you don’t need to worry about it here. Read more: https://github.com/11ty/eleventy/issues/2310
[@11ty/eleventy-upgrade-help] PASSED `eleventyConfig.ignores` are no longer re-used for the file watcher during --watch and --serve. If you’d like files to be ignored by the file watcher (to avoid triggering new builds), use the new dedicated `eleventyConfig.watchIgnores` API instead. This project doesn’t seem to be making use of the feature. Read more: https://www.11ty.dev/docs/watch-serve/#ignore-watching-files
[@11ty/eleventy-upgrade-help] PASSED Browsersync is no longer the default Development Server in Eleventy. This project doesn’t seem to be making use of any custom Browsersync options, so it’s unlikely to be affected! Learn more: https://www.11ty.dev/docs/dev-server/
[@11ty/eleventy-upgrade-help] PASSED Global data files with one or more dots in the file name are stored differently in the data cascade in Eleventy 2.0. For example, `a.b.json` stores as `'a.b': value` instead of `a: { b: value }`. This project has no affected data file paths. Read more: https://github.com/11ty/eleventy/pull/1912
[@11ty/eleventy-upgrade-help] PASSED This project is not using the removed `renderData` feature. Read more about `renderData`: https://github.com/11ty/eleventy/issues/2356
[@11ty/eleventy-upgrade-help] PASSED When calculating `page.fileSlug` dates are now stripped from parent folder names of index.* files. This project has no file/directory paths that are affected, no worries here. Read more: https://github.com/11ty/eleventy/pull/2111
[@11ty/eleventy-upgrade-help] This plugin is intended for temporary use: once you’re satisfied please remove this plugin from your project!