JustinGrote
commented
2 hours ago For example, the PowerShell extension is forced to use these unsupported engines due to maintaining Azure Data Studio Support
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@vscode/vsce@3.1.0',
npm WARN EBADENGINE required: { node: '>= 20' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'cheerio@1.0.0',
npm WARN EBADENGINE required: { node: '>=18.17' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'glob@11.0.0',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'minimatch@10.0.1',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'jackspeak@4.0.1',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'path-scurry@2.0.0',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'lru-cache@11.0.1',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: 'undici@6.19.8',
npm WARN EBADENGINE required: { node: '>=18.17' },
npm WARN EBADENGINE current: { node: 'v18.15.0', npm: '9.9.3' }
npm WARN EBADENGINE }
Azure Data studio is still running on electron 25. Electron 25 has been EOL for 9 months now and has several high and critical severity outstanding vulnerabilities that will never be fixed. Extensions such as the PowerShell extension that support Azure Data Studio also cannot update from the underlying nodejs version and are at risk for the same vulnerabilities.
Please consider updating to at least Electron
30.4.0which is what the current version of VSCode uses, I imagine with that user base it has been proven stable enough :).