⏬ Add mechanism for downgrading MyST AST #1734
Conversation
|
| }) | ||
| ) { | ||
| try { | ||
| const response = await fetch(`http://localhost:9000/${downgradeCachePath}`); |
There was a problem hiding this comment.
What are your thoughts on just treating this as a normal npm package that we install in the _build directory and check for updates (in the same way we do for mystmd now)?
Then there would be a version check against npm for that package, an npm install (already doing that for the themes).
That would mean we don't have to host these, we have versions, publishing, deprecations, etc. AND other tools can use this in a normal way - it is just a package.
As outlined in #1724, as the MyST user-base grows, we are increasingly likely to find ourselves in a situation whereby we feel reluctant to make breaking changes to our AST due to the impact upon the wider ecosystem of published knowledge.
We already know of one breaking change (e.g. #1671), and it is not unlikely that there will be more in coming releases.
This PR introduces a mechanism for legacy
mystmdapplications to handle newer AST through a downgrade process. We would also need to use the same approach formyst-theme. Ideally, these will use the same downgrade bundles (with different build targets if needs be).Closes #1724