npm/npmjs/@types/qs/6.9.11
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia
Hi @wbeaton . I want to point-out a bottle-neck in the current License check workflow, with @types/*
so-called "DefinitelyTyped" npm packages. These packages contain TypeScript type definitions, used during development, for the corresponding library(es). This ticket is an example/symptom.
As of today, close to 8000 npm packages have their definition files in GitHub repo DefinitelyTyped. There are so many that the web UI is unable to show them all:
The IP Bot seems unable to figure-out how to download the source code for these packages - the GitHub source link resolves to this page rather than real sources:
I think the IP Bot relies on the fact that the target repository will have tags matching the version of the package in question, which is not true with such a repository. In turn, failing to obtain sources, causes tickets such as this one here, to need be reviewed by the IP team, which obviously takes time.
Do you see a way forward? e.g. could the IP Bot be enhanced to handle this special repository better?
Thanks, Marc
npm/npmjs/@types/qs/6.9.10
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/theia-trace-extension.git
npm/npmjs/@types/qs/6.9.11
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia
npm/npmjs/@babel/helper-module-imports/7.24.3
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/tsp-typescript-client.git
npm/npmjs/@babel/code-frame/7.24.2
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/tsp-typescript-client.git
npm/npmjs/@babel/core/7.24.3
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/tsp-typescript-client.git
npm/npmjs/@babel/highlight/7.24.2
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/tsp-typescript-client.git
We merged a PR that gets rid of the deprecated version of this 3PP (0.3.0): https://github.com/eclipse-cdt-cloud/vscode-trace-extension/pull/215
I think we can close this ticket - thanks Rahul!
npm/npmjs/@types/node/20.11.17
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/vscode-trace-server.git
npm/npmjs/-/allure-js-commons/2.14.0
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/theia-trace-extension.git
npm/npmjs/-/allure-playwright/2.14.0
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/theia-trace-extension.git
npm/npmjs/-/playwright-core/1.42.1
Project: ecd.cdt-cloud
Repository: https://github.com/eclipse-cdt-cloud/theia-trace-extension.git
Hi Rahul,
As it's currently used, that dependency is being pulled indirectly, by something we depend-on, rather than directly. I will see if we can update the whole chain.
npm/npmjs/-/allure-commandline/2.27.0
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia
npm/npmjs/-/socket.io-adapter/2.5.4
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia
npm/npmjs/-/node-abi/3.56.0
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia
npm/npmjs/-/allure-commandline/2.27.0
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia
npm/npmjs/-/allure-playwright/2.13.0
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia
npm/npmjs/@vscode/vsce/2.24.0
Project: ecd.theia
Repository: https://github.com/eclipse-theia/theia