Releases: hashicorp/next-mdx-enhanced
v2.1.0 - Add `scan` option for layout customization
v2.0.1
v2.0.0
This is a potentially breaking release!
When accessing the synthetic frontmatter property __resourcePath
via layout file, previously this value would have no leading slash, however, when importing frontmatter, the property would have a leading slash. Now, when importing frontmatter there is no longer a leading slash, and the two properties are exactly the same between layout and import.
If you were importing a file's frontmatter and using the __resourcePath
property for anything, make sure to double check the place you were using it to ensure that the removal of the leading slash will not break your code.
v1.2.1
v1.2.0
This release contains a minor fixes that should not impact most usage.
First, if you were using symlinked mdx files, you would get errors previously. This should now be resolved, and symlinks can be used without issue with this plugin now.
Second, if there were yaml errors in any of the mdx files processed, previously the error message would be unclear and it would be difficult to pin down where it came from. Now, yaml errors are handled properly and are perfectly clear with an error message, file source, and line/column trace.
And finally, we now use safeLoad
instead of load
for frontmatter, which closes down some opportunities to inject strange behavior.
v1.1.1
Small bugfix for a silly mistake - fixes the previous release
Change summary: v1.1.0...v1.1.1
v1.1.0
This plugin now works on windows!
v1.0.0
This is a non-breaking upgrade, but since the package is stable and used in production we're going to 1.0
.
This release updates to the latest version of prebuild-webpack-plugin
which drastically improves performance. It also fixes a small issue with asset hashing so that hashes are the same between any environment, as well as upgrades tests, CI, and dependencies.
This should be a simple upgrade with no changes that makes your local dev experience about 5x faster than it was before. Whoo! 🎉
Commits since last release: v0.8.0...v1.0.0
v0.8.0
v0.7.0
Removes babel.createConfigItem, as it causes dependency bugs and seems to be useless