⚙️ Site build config for compatibility

[JFWooten4]

I've been grappling with this for years now, and I'm finally proposing we add cross-env. There's just a lot of cool things we can optimize with this between systems.

As you add more meetings over time, the build size compounds with the new pages. It's still very reasonable linear building, but you hit the max compile chunk after about a hundred or so.

This little fix gives the compiler some more memory, or at least the preview history. It's nothing fancy, but it stops heap mallocs.

Lastly, I ran into a problem where TypeScript ran with the wrong version based on complaints of global settings. This little VS Code config makes sure it uses the version for the project.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cross-env@​10.1.0

View full report

[Copilot]

Pull request overview

Updates the docs site build tooling/config to improve cross-system compatibility by adjusting the build command’s Node memory settings, adding cross-env, and ensuring VS Code uses the workspace TypeScript version.

Changes:

• Updated the build script to run Docusaurus with an increased Node heap limit.
• Added cross-env (and corresponding yarn.lock entries).
• Added a VS Code workspace setting to point to the repo’s TypeScript SDK.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.

File	Description
package.json	Changes build invocation and adds cross-env to devDependencies.
yarn.lock	Locks cross-env and its new transitive dependency.
.vscode/settings.json	Adds a workspace TypeScript SDK path for VS Code.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.