Building 2022.09.120 is broken

[realratchet]

I have tried building the previous version of the extension (2022.09.120), however, the build seems to be completely broken. Seems to be related to incompatible type definitions being pulled. Any way to resolve this? Since this is an older build I'm unlikely to get help and feel like raising an issue would be inadequate so I'm trying my luck here.

./src/notebooks/debugger/debuggingManager.ts 282:20-45
[tsl] ERROR in ~/vscode-jupyter/src/notebooks/debugger/debuggingManager.ts(282,21)
      TS2322: Type '{ debugUI: { simple: boolean; }; suppressSaveBeforeStart: true; } | { suppressSaveBeforeStart: true; }' is not assignable to type 'DebugSessionOptions | undefined'.
  Type '{ debugUI: { simple: boolean; }; suppressSaveBeforeStart: true; }' is not assignable to type 'DebugSessionOptions'.
    Object literal may only specify known properties, and 'debugUI' does not exist in type 'DebugSessionOptions'.
 @ ./src/notebooks/serviceRegistry.web.ts 24:27-65
 @ ./src/extension.web.ts 30:30-72

ERROR in ~/vscode-jupyter/src/test/datascience/jupyterPasswordConnect.unit.test.ts
341:51-56
[tsl] ERROR in ~/vscode-jupyter/src/test/datascience/jupyterPasswordConnect.unit.test.ts(341,52)
      TS2345: Argument of type 'MockInputBox' is not assignable to parameter of type 'InputBox'.
  Property 'valueSelection' is missing in type 'MockInputBox' but required in type 'InputBox'.

ERROR in ~/vscode-jupyter/src/test/datascience/mockInputBox.ts
7:13-25
[tsl] ERROR in ~/vscode-jupyter/src/test/datascience/mockInputBox.ts(7,14)
      TS2420: Class 'MockInputBox' incorrectly implements interface 'InputBox'.
  Property 'valueSelection' is missing in type 'MockInputBox' but required in type 'InputBox'.

ERROR in ~/vscode-jupyter/src/test/datascience/jupyter/serverSelector.unit.test.ts
62:59-64
[tsl] ERROR in ~/vscode-jupyter/src/test/datascience/jupyter/serverSelector.unit.test.ts(62,60)
      TS2345: Argument of type 'MockInputBox' is not assignable to parameter of type 'InputBox'.

ERROR in ~/vscode-jupyter/src/test/mocks/vsc/extHostedTypes.ts
1112:16-29
[tsl] ERROR in ~/vscode-jupyter/src/test/mocks/vsc/extHostedTypes.ts(1112,17)
      TS2322: Type '((MarkdownString | MarkedString) & IMarkdownString)[]' is not assignable to type 'MarkdownString[] | MarkedString[]'.
  Type '((MarkdownString | MarkedString) & IMarkdownString)[]' is not assignable to type 'MarkdownString[]'.
    Type '(MarkdownString | MarkedString) & IMarkdownString' is not assignable to type 'MarkdownString'.
      Type 'String & IMarkdownString' is missing the following properties from type 'MarkdownString': appendText, appendMarkdown, appendCodeblock

ERROR in ~/vscode-jupyter/src/test/mocks/vsc/extHostedTypes.ts
1114:16-29
[tsl] ERROR in ~/vscode-jupyter/src/test/mocks/vsc/extHostedTypes.ts(1114,17)
      TS2322: Type '(MarkdownString | MarkedString)[]' is not assignable to type 'MarkdownString[] | MarkedString[]'.
  Type '(MarkdownString | MarkedString)[]' is not assignable to type 'MarkdownString[]'.
    Type 'MarkdownString | MarkedString' is not assignable to type 'MarkdownString'.
      Type 'string' is not assignable to type 'MarkdownString'.

6 errors have detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.

2022-12-14 14:37:06: webpack 5.71.0 compiled with 6 errors in 45616 ms

    at buildWebPack (~/vscode-jupyter/gulpfile.js:297:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async buildWebPackForDevOrProduction (~/vscode-jupyter/gulpfile.js:198:9)
    at async ~/vscode-jupyter/gulpfile.js:222:5
[14:37:07] 'webpack' errored after 1.13 min```

[amunger]

looks like it may have not updated the vscode API definitions correctly.
Have you tried with a clean repo?
git clean -fxd
npm ci
reload vscode
build

[realratchet]

This was with fresh pull of a repo, but I tried just in case the issue persists. Although this part reload vscode seems strange, I'm attempting to build with a never vscode for an older vscode version. Does the host vscode version matter?

I'll attempt to build it with an older vscode version later too.

[amunger]

yes, it does matter. The extension is launched inside the same version of vs code that you are using to develop. So if a proposed API was dropped or had a breaking change, it would no longer work with later versions.

[realratchet]

Didn't think about it because I never intended to launch it only to run the npm package script for another machine that has an older engine. I'll see if that helps when I have more time.

[realratchet]

Unfortunately didn't help npm run package still fails.