chore(deps): update dependency remark-frontmatter to v3 #1294
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
* Move `remark-mdx*` packages to `remark-mdxjs` * Rename * Add `remark-mdx` * Add tests * Ignore `remark-mdx` * Remove husky for now * done * Update comment syntax in the docs * Add back all file extensions for eslint * Remove comments for now and eslint-mdx temporarily * Remove comments for now, add redirect to mdx-provider in docs * Missed a merge conflict * Fix eslint Co-authored-by: John Otander <[email protected]>
…/runtime, and @mdx-js/vue (#1079)
…ts, remark-mdx-remove-imports, @mdx-js/util (#1082)
* Improve export name extraction Many different types of export syntax wasn't supported, primarily destructuring for objects and arrays. This adds export extraction to the import name extraction step so we can more accurately determine what shortcodes to generate. * Place gatsby-plugin-mdx in the root for now, seems to not be resolving properly * Fix linting * Make null handling more clear * Fix handling of null specifiers * Move dep to proper place
* Fix linting * Fix error in remark formatter
I'm not sure we need to run such a complex test matrix because it unfortunately makes CI pretty slow. Here I propose removing node v12 and MacOS.
dependency updates may help resolve flaky tests which have been occuring on `next` branch
Co-authored-by: Renovate Bot <[email protected]>
* Add MDX Embed guide to readme * Move to guides
Related to GH-1271.
Closes GH-1414 Reviewed-by: Christian Murphy <[email protected]>
* Update `react`, `react-dom` * Clean Next, Razzle, Vue examples * Update parcel example, parcel plugin, run tests * Prefer `.mdx` extension over `.md` * This does not yet touch CRA * It’s impossible to get Gatsby working in our workspace (they fork MDX but resolve from their dependency on old MDX) * I can’t get webpack 5 working either Related to GH-1292. Closes GH-1415. Reviewed-by: Christian Murphy <[email protected]>
Co-authored-by: Renovate Bot <[email protected]>
Closes GH-1344. Reviewed-by: Christian Murphy <[email protected]> Reviewed-by: Titus Wormer <[email protected]>
Create React App is the most looked at resource by users here on GitHub. But it’s suggesting an old, unmaintained, and buggy way to use MDX. This instead updates the guide to use our maintained projects, without having to eject from CRA. As CRA itself is an ever-changing “init” tool, which can support MDX by following a couple steps, I don’t think it’s wise to have an example in the project: we want folks to do `npx create-react-app ...`, not clone our custom example. Not having CRA checked in also makes for a faster `yarn install`. Perhaps developing our own [CRA template](https://create-react-app.dev/docs/custom-templates) might be nice for the future, but for now I’ve kept it at an up to date and working guide. Related to GH-1015. Related to GH-1388. Closes GH-365. Closes GH-589. Closes GH-1422. Reviewed-by: Christian Murphy <[email protected]>
Closes GH-1427. Reviewed-by: Christian Murphy <[email protected]> Reviewed-by: Titus Wormer <[email protected]>
* Update docs to lazy load stored dark mode preference * Add support for prefers-color-scheme for dark mode
L39 says: > If you only want the loader for `.mdx` files you can _change_ the regex to `/\.mdx$/`. So I suppose the RegExp in the sample config should have be `test: /\.mdx?$/`.
Co-authored-by: Christian Murphy <[email protected]>
* ci: simplify ci workflows, change master to main on ci * ci: reset git status before publishing * ci: run `git status` before resetting
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-remark-monorepo
branch
from
d2ef44f
to
7d1b850
Compare
Renovate Ignore NotificationAs this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 3.x releases. However, if you upgrade to 3.x manually then Renovate will then reenable updates for minor and patch updates automatically. If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.0.0->^3.0.0Release Notes
remarkjs/remark-frontmatter
v3.0.0Compare Source
fb1357bUpdate formicromarkinremark@13(breaking, this update will not work for remark lower than v13, see commit for changes)
Renovate configuration
📅 Schedule: "before 3am on Monday" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.