Skip to content
Closed
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
64 changes: 32 additions & 32 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",
"@algolia/autocomplete-js": "^1.19.8",
"@algolia/autocomplete-theme-classic": "^1.19.8",
"@babel/cli": "^7.28.6",
"@babel/core": "^7.29.0",
"@babel/preset-env": "^7.29.5",
"@babel/preset-typescript": "^7.14.5",
"@babel/runtime": "^7.26.10",
"@datadog/browser-logs": "^4.29.1",
"@datadog/browser-rum": "^4.29.1",
"@babel/runtime": "^7.29.2",
"@datadog/browser-logs": "^7.1.0",
"@datadog/browser-rum": "^7.1.0",
"@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.19",
"@types/dotenv-defaults": "^2.0.1",
"@types/lodash.chunk": "^4.2.6",
"@types/node": "^25.0.3",
"@types/node": "^25.9.1",
"@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.

P1 Badge Initialize Alpine explicitly after upgrading to v3

This bumps alpinejs from v2 to v3, but the site bootstrap still uses the old side-effect import (website/assets/js/app.js has import 'alpinejs') and never calls Alpine.start(). With Alpine v3 module usage, that explicit start is required; without it, Alpine directives (x-data, x-show, event handlers) across the templates won’t initialize, breaking interactive behavior like navigation toggles and global UI state updates.

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.3",
"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",
"postcss-cli": "^11.0.1",
"postcss-import": "^16.1.1",
"react": "^19.2.6",
"react-dom": "^19.2.6",
"react-spring": "^10.0.3",
"react-use": "^17.2.4",
"regenerator-runtime": "^0.13.7",
"tailwindcss": "^2.2.4",
"tocbot": "^4.12.2",
"regenerator-runtime": "^0.14.1",
"tailwindcss": "^4.3.0",

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 Tailwind PostCSS plugin for v4 upgrade

Upgrading tailwindcss to ^4.3.0 without also adding @tailwindcss/postcss breaks the website CSS build path, because this repo still runs CSS through PostCSS (website/config.toml has postcss = true) and website/postcss.config.js loads tailwindcss as a PostCSS plugin (import tailwindCss from "tailwindcss" and uses it in plugins). In Tailwind v4, that direct plugin usage is no longer supported, so Hugo/PostCSS compilation will fail until the config and dependency are migrated.

Useful? React with 👍 / 👎.

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 Replace removed @tailwind directives for Tailwind v4

The dependency bump moves Tailwind from v2 to v4, but the stylesheet entrypoint still uses legacy directives (website/assets/css/style.css starts with @tailwind base;, @tailwind components;, @tailwind utilities;). In v4 these directives were removed in favor of @import "tailwindcss", so leaving them unchanged causes the website CSS pipeline to fail or generate incorrect output even after fixing the PostCSS plugin package.

Useful? React with 👍 / 👎.

"tocbot": "^4.36.8",
"topojson-client": "^3.1.0",
"tsx": "^4.21.0",
"typescript": "^5.9.3",
"typesense": "^1.8.2",
"tsx": "^4.22.3",
"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.3",
"prettier-plugin-go-template": "^0.0.15"
}
}
Loading
Loading