Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
68 changes: 34 additions & 34 deletions website/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,60 +9,60 @@
"lighthouse": "lighthouse --output html --output-path ./reports/lighthouse.html --view https://vector.dev"
},
"dependencies": {
"@algolia/autocomplete-js": "^1.2.1",
"@algolia/autocomplete-theme-classic": "^1.2.1",
"@babel/cli": "^7.14.5",
"@babel/core": "^7.14.6",
"@babel/preset-env": "^7.14.5",
"@babel/preset-typescript": "^7.14.5",
"@babel/runtime": "^7.26.10",
"@datadog/browser-logs": "^4.29.1",
"@datadog/browser-rum": "^4.29.1",
"@algolia/autocomplete-js": "^1.19.8",
"@algolia/autocomplete-theme-classic": "^1.19.8",
"@babel/cli": "^8.0.1",
"@babel/core": "^8.0.1",
"@babel/preset-env": "^8.0.2",
"@babel/preset-typescript": "^8.0.1",
Comment on lines +15 to +17

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Migrate Babel config before moving to v8

This upgrades the Babel toolchain to v8, but website/babel.config.js still passes options that Babel 8 removed or changed (useBuiltIns/corejs for preset-env and isTSX/allExtensions for preset-typescript). Hugo Pipes runs babel for the React search/home bundles, so preview/production builds that reach JS compilation will fail until the Babel config is migrated or these packages stay on v7.

Useful? React with 👍 / 👎.

"@babel/runtime": "^8.0.0",
"@datadog/browser-logs": "^7.3.0",
"@datadog/browser-rum": "^7.3.0",
Comment on lines +19 to +20

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve console error forwarding when upgrading Datadog

When production monitoring relies on browser console.error diagnostics, this v7 bump changes behavior: website/assets/js/dd-browser-logs-rum.js initializes Logs with forwardErrorsToLogs: true but no forwardConsoleLogs, and Datadog v7 makes those controls independent instead of forwarding console errors implicitly. Add forwardConsoleLogs: ['error'] (or intentionally document the drop) to avoid losing those production log events after the upgrade.

Useful? React with 👍 / 👎.

"@emotion/babel-preset-css-prop": "^11.2.0",
"@fullhuman/postcss-purgecss": "^4.0.3",
"@fullhuman/postcss-purgecss": "^8.0.0",
"@iarna/toml": "^2.2.5",
"@ryangjchandler/spruce": "^2.6.3",
"@tailwindcss/forms": "^0.3.2",
"@tailwindcss/typography": "^0.4.1",
"@tailwindcss/forms": "^0.5.11",
"@tailwindcss/typography": "^0.5.20",
"@types/dotenv-defaults": "^2.0.1",
"@types/lodash.chunk": "^4.2.6",
"@types/node": "^25.0.3",
"@types/node": "^26.0.0",
"@types/topojson-specification": "^1.0.1",
"alpinejs": "^2.8.2",
"autoprefixer": "^10.2.5",
"alpinejs": "^3.15.12",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Initialize Alpine v3 instead of relying on v2 startup

The Alpine package is upgraded from v2 to v3, but assets/js/app.js still only does a bare import 'alpinejs' and registers the Spruce store without ever importing Alpine and calling Alpine.start() after setup. With the npm/module build in Alpine v3, that means the many x-data, x-show, and @click bindings in the layouts will not initialize, breaking dark mode, dropdowns, download selectors, and other page interactions.

Useful? React with 👍 / 👎.

"autoprefixer": "^10.5.0",
"babel-preset-next": "^1.4.0",
"chalk": "^4.1.1",
"cheerio": "^1.0.0-rc.5",
"chalk": "^5.6.2",
"cheerio": "^1.2.0",
"classnames": "^2.3.1",
"core-js": "^3.14.0",
"core-js": "^3.49.0",
"crypto": "^1.0.1",
"d3-geo": "^3.0.1",
"domhandler": "^4.2.0",
"dotenv-defaults": "^2.0.2",
"downshift": "^6.1.3",
"glob-promise": "^4.2.0",
"domhandler": "^6.0.1",
"dotenv-defaults": "^6.0.0",
"downshift": "^9.3.6",
"glob-promise": "^6.0.7",
"lodash.chunk": "^4.2.0",
"path": "^0.12.7",
"postcss-cli": "^8.3.1",
"postcss-import": "^14.0.1",
"react": "^19.2.3",
"react-dom": "^19.2.3",
"react-spring": "^10.0.3",
"react-use": "^17.2.4",
"regenerator-runtime": "^0.13.7",
"tailwindcss": "^2.2.4",
"tocbot": "^4.12.2",
"postcss-cli": "^11.0.1",
"postcss-import": "^16.1.1",
"react": "^19.2.7",
"react-dom": "^19.2.7",
"react-spring": "^10.0.4",
"react-use": "^17.6.1",
"regenerator-runtime": "^0.14.1",
"tailwindcss": "^4.3.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Use the Tailwind v4 PostCSS plugin before upgrading

This bump selects Tailwind 4, but the website still runs Hugo's PostCSS pipeline for css/style.css and postcss.config.js still imports/uses tailwindcss directly as a PostCSS plugin. Tailwind v4 moved that plugin to @tailwindcss/postcss, which is not added here, so preview/production Hugo builds that process CSS will fail before emitting the site instead of just picking up the dependency update.

Useful? React with 👍 / 👎.

"tocbot": "^4.36.8",
"topojson-client": "^3.1.0",
"tsx": "^4.22.4",
"typescript": "^5.9.3",
"typesense": "^1.8.2",
"typescript": "^6.0.3",
"typesense": "^3.0.6",
"typesense-sync": "https://s3.amazonaws.com/origin-static-assets/corp-node-packages/master/typesense-sync-v2.0.0.tgz"
},
"browserslist": [
"since 2017-06"
],
"devDependencies": {
"prettier": "^3.5.3",
"prettier": "^3.8.4",
"prettier-plugin-go-template": "^0.0.15"
}
}
Loading
Loading