Releases
v2.0.0
Compare
Sorry, something went wrong.
No results found
Breaking Changes
Eliminated manual file copying requirement - Plugin now uses Docusaurus native APIs
Users upgrading from v1.x must remove manually copied theme files (src/theme/Root.js and src/components/MarkdownActionsDropdown/)
Component directory structure changed: src/ → theme/ and components/
Components now bundled with plugin instead of user's project
Added
getThemePath() plugin API to automatically provide theme components
.gitignore file for cleaner development experience
Comprehensive migration guide in README for v1.x users
Zero-config installation - just add plugin to docusaurus.config.js
Changed
Plugin now provides components via Docusaurus plugin APIs instead of requiring manual copying
Updated README with simplified installation instructions
Component imports now use relative paths instead of @site alias
Updated troubleshooting guide to reflect new architecture
Updated advanced configuration examples to use swizzling
Improved
Much better developer experience - no manual file management needed
Components automatically update when plugin updates (no stale copied files)
Cleaner project structure - plugin consumers don't need theme overrides
Standard Docusaurus plugin pattern - follows best practices
Technical Details
Uses Docusaurus getThemePath() lifecycle method
Components bundled at: theme/Root.js and components/MarkdownActionsDropdown/
Tested in production with 58 markdown files and 10 image directories
Compatible with Docusaurus v3.x
Migration from v1.x
Remove manually copied files: src/theme/Root.js and src/components/MarkdownActionsDropdown/
Update the plugin: npm update docusaurus-markdown-source-plugin
Rebuild: npm run build
CSS in custom.css remains unchanged
You can’t perform that action at this time.