-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade mdx to v3 #13
Conversation
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. What is shell access?This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code. Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
5f22045
to
df04000
Compare
847cb39
to
cc62ef9
Compare
cc62ef9
to
929b700
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. But I think this should be a major
change, just in case.
337e14c
to
cff7cf3
Compare
package.json
Outdated
"@babel/core": "^7.12.3", | ||
"@babel/parser": "^7.12.11", | ||
"@babel/preset-env": "^7.12.1", | ||
"@babel/preset-typescript": "^7.13.0", | ||
"@babel/traverse": "^7.12.11", | ||
"@babel/types": "^7.14.8", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we are doing a major release, let's also update all babel dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing! They only upgraded in minor though
cff7cf3
to
cc7f292
Compare
Issue: #
What Changed
This PR upgrades
@mdx/mdx-js
to v3. It also upgrades yarn from v1 to v4, as well as replaces Jest with Vitest.There was an issue with mapped imports introduced in a new version of vfile (dependency of mdx) which caused this in the test run:
Vitest was able to identify these imports without issues. I don't know whether this could cause problems in a Webpack project, I'll have to check with a canary release of Storybook using this canary release.
How to test
Change Type
maintenance
documentation
patch
minor
major
📦 Published PR as canary version:
0.1.1--canary.13.0f9c1e4.0
✨ Test out this PR locally via:
Version
Published prerelease version:
v0.1.1-next.2
Changelog
💥 Breaking Change
next
Authors: 2