Upgrade Lit Typescript Starter Dependencies

[fireflysemantics]

Should this be an RFC?

• This is not a substantial change

Which package is this a feature request for?

Starter Kits (@lit/lit-starter-js / @lit/lit-starter-ts)

Description

It would be great if the dependencies for the Typescript starter kit were updated.

These are the latest versions of all the packages ( Found by running ncu).

 @11ty/eleventy                          ^1.0.1  →   ^2.0.1
 @11ty/eleventy-plugin-syntaxhighlight   ^4.0.0  →   ^5.0.0
 @custom-elements-manifest/analyzer      ^0.6.3  →  ^0.10.2
 @open-wc/testing                        ^3.1.5  →   ^4.0.0
 @rollup/plugin-node-resolve            ^13.3.0  →  ^15.2.3
 @rollup/plugin-replace                  ^5.0.2  →   ^5.0.6
 @typescript-eslint/parser              ^5.25.0  →  ^7.12.0
 @web/dev-server                        ^0.1.31  →   ^0.4.5
 @web/dev-server-legacy                  ^1.0.0  →   ^2.1.1
 @web/test-runner                       ^0.15.0  →  ^0.18.2
 @web/test-runner-playwright             ^0.9.0  →  ^0.11.0
 eslint                                 ^8.15.0  →   ^9.4.0
 lit                                     ^3.0.0  →   ^3.1.4
 lit-analyzer                            ^1.2.1  →   ^2.0.3
 prettier                                ^2.6.2  →   ^3.3.1
 rimraf                                  ^3.0.2  →   ^5.0.7
 rollup                                 ^2.73.0  →  ^4.18.0
 rollup-plugin-summary                   ^1.4.3  →   ^2.0.1
 typescript                              ~5.3.3  →   ~5.4.5

Alternatives and Workarounds

Users can just upgrade themselves.

npm install -g npm-check-updates
ncu -u

Just running ncu reports on which packages can be upgraded.

[fireflysemantics]

Also https://www.npmjs.com/package/rollup-plugin-terser is deprecated.

The replacement is:
https://www.npmjs.com/package/@rollup/plugin-terser

[fireflysemantics]

I used this install sequence to attempt an upgrade (All except eslint could be upgraded. Trying to upgrade eslint fails due to pair dependency constraints).

npm uninstall rollup-plugin-terser && npm i -D typescript@latest @rollup/plugin-terser@latest rollup-plugin-summary@latest @rollup/plugin-node-resolve@latest rollup @web/dev-server rimraf@latest prettier@latest lit-analyzer@latest lit@latest  @web/test-runner-playwright@latest @web/test-runner@latest @web/dev-server-legacy@latest  @web/dev-server@latest @rollup/plugin-replace@latest @rollup/plugin-node-resolve@latest @open-wc/testing@latest @custom-elements-manifest/analyzer@latest @11ty/eleventy@latest @11ty/eleventy-plugin-syntaxhighlight@latest @typescript-eslint/parser@latest

[fireflysemantics]

Some notes about the dependency upgrade ... It's a little tricky ...

https://stackoverflow.com/questions/78589746/node-unable-to-resolve-dependency-tree?noredirect=1#comment138553081_78589746

[fireflysemantics]

OK - I realized that I forgot to include the @typescript-eslint/eslint-plugin@latest dependency in the commandline install ....this new install sequence updates everything correctly ...

npm uninstall rollup-plugin-terser && npm i -D typedoc@latest typescript@latest @rollup/plugin-terser@latest rollup-plugin-summary@latest @rollup/plugin-node-resolve@latest rollup@latest @web/dev-server@latest rimraf@latest prettier@latest lit-analyzer@latest lit@latest  @web/test-runner-playwright@latest @web/test-runner@latest @web/dev-server-legacy@latest  @web/dev-server@latest @rollup/plugin-replace@latest @rollup/plugin-node-resolve@latest @open-wc/testing@latest @custom-elements-manifest/analyzer@latest @11ty/eleventy@latest @11ty/eleventy-plugin-syntaxhighlight@latest @types/mocha @typescript-eslint/eslint-plugin@latest
 @typescript-eslint/parser@latest

One thing to note is that if it is run with the current dependencies declared in package.json with the current versions, the install will still fail due to peer dependency conflicts that npm "thinks" is present. I had to delete the dependency declarations for typescript eslint to get a clean install. So removing these before doing the update will remove the peer dependency conflict errors.

Note that the very latest eslint and the typescript parser and plugin 
cause peer dependency constraint issues, so delete these dependencies
from `package.json` before doing the install.

"@typescript-eslint/eslint-plugin": "^5.25.0",
"@typescript-eslint/parser": "^5.25.0",

[drk-mtr]

I haven't tested everything, but it looks like putting this in package.json and running npm install should work.

Notes:

1. eslint version held back to v8, since @typescript-eslint v7 requires this.
2. rimraf and blob versions overridden to avoid annoying warnings.

  "dependencies": {
    "lit": "^3.1.4"
  },
  "devDependencies": {
    "@11ty/eleventy": "^2.0.1",
    "@11ty/eleventy-plugin-syntaxhighlight": "^5.0.0",
    "@custom-elements-manifest/analyzer": "^0.10.3",
    "@open-wc/testing": "^4.0.0",
    "@rollup/plugin-node-resolve": "^15.2.3",
    "@rollup/plugin-replace": "^5.0.7",
    "@rollup/plugin-terser": "^0.4.4",
    "@typescript-eslint/eslint-plugin": "^7.16.0",
    "@typescript-eslint/parser": "^7.16.0",
    "@web/dev-server": "^0.4.6",
    "@web/dev-server-legacy": "^2.1.1",
    "@web/test-runner": "^0.18.2",
    "@web/test-runner-playwright": "^0.11.0",
    "@webcomponents/webcomponentsjs": "^2.8.0",
    "eslint": "^8.57.0",
    "lit-analyzer": "^2.0.3",
    "prettier": "^3.3.3",
    "rimraf": "^6.0.1",
    "rollup": "^4.18.1",
    "rollup-plugin-summary": "^2.0.1",
    "typescript": "~5.5.3"
  },
  "overrides": {
    "rimraf": "$rimraf",
    "glob": "^11.0.0"
  },