chore(deps): update dependencies

[martinalbert]

npm-check-updates output:

 @rushstack/eslint-patch     ^1.1.0  →     ^1.2.0
 @types/node              ^16.11.26  →  ^18.11.18
 @vitejs/plugin-vue          ^2.2.2  →     ^4.0.0
 buttercms                   ^1.2.8  →     ^1.2.9
 eslint                      ^8.5.0  →    ^8.32.0
 eslint-plugin-vue           ^8.2.0  →     ^9.9.0
 prettier                    ^2.5.1  →     ^2.8.3
 vite                        ^2.8.4  →     ^4.0.4
 vue                        ^3.2.31  →    ^3.2.45
 vue-router                 ^4.0.12  →     ^4.1.6
 vue-tsc                    ^0.31.4  →    ^1.0.24

Major changes

• mainly ending support for lower versions of node or some specific changes in api, check links for more details.
• @types/node
  • v17 major changes
  • v18 major changes
• @vitejs/plugin-vue
  • v3 changes
  • v4 changes
• eslint-plugin-vue - v9 changes
• vite - node EOL, major rollup releases, browser releases and more
  • v3 changes (migration guide)
  • v4 changes (migration guide)
• vue-tsc - few breaking changes regarding vueCompilerOptions and extensions (more info here)

npm audit

• on main branch found 2 vulnerabilities (1 moderate, 1 critical)
• after npm audit fix found 0
• after update of dependencies listed above found also 0

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated
vuejs-starter-buttercms	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 30, 2023 at 10:26AM (UTC)

[ViolanteCodes]

@martinalbert does this need to be updated: https://share.getcloudapp.com/NQu4924O

[ViolanteCodes]

@martinalbert second question - i see this now runs on localhost:5173 instead of 3000. This seems like a very minor change - but there are a number of places throughout our website and materials where this starter project is already featured and instructions already exist to run on localhost:3000. Is it possible to add a configuration setting somewhere that forces this to 3000? or is that behavior not preferred for some reason?

[martinalbert]

@ViolanteCodes regarding the recommended node version, it seems like updates are about dropping support of node v12 or v14, so 16 should be still ok, unless you'll use something new from @types/node or vite which uses node v18. I would have to dig deeper to check if everything that you use is compatible with v16.

Regarding the port, you're right, I can change the port to 3000.