upgrade to docusaurus v3

[smblee]

No description provided.

[vercel]

@smblee is attempting to deploy a commit to the Uniswap Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 11, 2024 6:41pm

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Possible typosquat attack	npm/[email protected]	Did you mean: v8-compile-cache**-lib**	yarn.lock	🚫
Filesystem access	npm/[email protected]	Module: fs/promises Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	yarn.lock	⚠︎
Dynamic require	npm/[email protected]	Location: Package overview	yarn.lock	⚠︎
Dynamic require	npm/[email protected]	Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/@pnpm/[email protected]	Module: fs Location: Package overview	yarn.lock	⚠︎
Shell access	npm/[email protected]	Module: child_process Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	yarn.lock	⚠︎
Shell access	npm/[email protected]	Module: child_process Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	yarn.lock	⚠︎
Dynamic require	npm/@babel/[email protected]	Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/@docusaurus/[email protected]	Module: fs-extra Location: Package overview	yarn.lock	⚠︎
Filesystem access	npm/@docusaurus/[email protected]	Module: fs-extra Location: Package overview	yarn.lock	⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

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 dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@pnpm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@babel/[email protected]
• @SocketSecurity ignore npm/@docusaurus/[email protected]
• @SocketSecurity ignore npm/@docusaurus/[email protected]

[saucepoint]

flagging for myself -- the markdown files in v4/reference/* are generated with forge doc and copied to this repo's directory structure in uniswap/docs/scripts/v4-forge-doc.sh

I'll update the script and use sed to make sure we're escaping docusaurus v3 special characters

---

this shouldnt block our upgrade to docusaurus v3 tho

[smblee]

Could i get a ✅

[socket-security]

Report too large to display inline

View full report↗︎