pnp
Bug report: Issues while upgrading SPFx solution to v1.21.1 from 1.14.0
Priority
(Urgent) I can't use the CLI
Description
We are trying to upgrade a SPFx solution/project from version 1.14.0 to version 1.21.1 but facing issues while executing npm install given in step no. 3 from the given article.
Steps to reproduce
We are following below article.
Click here.
Expected results
npm install should exit without any error.
Actual results
PROJECT-PATH>npm install
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '[email protected]',
npm warn EBADENGINE required: { node: '>=22.14.0 < 23.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@microsoft/[email protected]',
npm warn EBADENGINE required: { node: '>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0' },
npm warn EBADENGINE current: { node: 'v18.20.5', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn deprecated [email protected]: This functionality has been moved to @npmcli/fs
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm warn deprecated [email protected]: The functionality that this package provided is now in @npmcli/arborist
npm warn deprecated [email protected]: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated [email protected]: This package is deprecated. Use https://socket.dev/npm/package/eta instead.
npm warn deprecated [email protected]: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm warn deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm warn deprecated [email protected]: This package is no longer supported. Please use @npmcli/package-json instead.
npm warn deprecated [email protected]: This module is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm warn deprecated [email protected]: this library is no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
npm warn deprecated [email protected]: use String.prototype.padStart()
npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm warn deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm warn deprecated @microsoft/[email protected]: Package no longer supported. Use at your own risk
npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm warn deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: spfx-uifabric-themes will not be maintained in future - checkout https://my.n8d.at/htwoo
npm warn deprecated @microsoft/[email protected]: Package no longer supported. Use at your own risk
npm warn deprecated [email protected]: This package is no longer supported. Please migrate to @azure/msal-angular.
npm warn deprecated @opentelemetry/[email protected]: Package renamed to @opentelemetry/api, see https://github.com/open-telemetry/opentelemetry-js
npm warn deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm warn deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm warn deprecated @material-ui/[email protected]: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm warn deprecated [email protected]: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm warn deprecated @azure/[email protected]: A newer major version of this library is available. Please upgrade to the latest available version.
npm warn deprecated @azure/[email protected]: A newer major version of this library is available. Please upgrade to the latest available version.
npm warn deprecated @azure/[email protected]: This package is no longer supported. Please migrate to use @azure/core-rest-pipeline
npm warn deprecated [email protected]: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm warn deprecated [email protected]: This package is no longer supported. Please use @azure/msal-browser instead.
npm warn deprecated [email protected]: This package is no longer supported. Please use @azure/msal-browser instead.
npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated [email protected]: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
npm warn deprecated [email protected]: This package is no longer supported. Please use @azure/msal-browser instead.
npm warn deprecated [email protected]: This package is no longer supported. Please use @azure/msal-browser instead.
npm warn deprecated [email protected]: This package is no longer supported. Please use @azure/msal-browser instead.
npm warn deprecated [email protected]: This package is no longer supported. Please use @azure/msal-browser instead.
npm warn deprecated @material-ui/[email protected]: Material UI v4 doesn't receive active development since September 2021. See the guide https://mui.com/material-ui/migration/migration-v4/ to upgrade to v5.
npm warn cleanup Failed to remove some directories [
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@microsoft\spfx-heft-plugins\node_modules\is-number',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules@microsoft\spfx-heft-plugins\node_modules\is-number'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@microsoft\spfx-heft-plugins\node_modules\is-number'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@microsoft\spfx-heft-plugins\node_modules',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules@microsoft\spfx-heft-plugins\node_modules\to-regex-range'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@microsoft\spfx-heft-plugins\node_modules\to-regex-range'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\webpack-dev-server',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules\webpack-dev-server\node_modules\mime'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\webpack-dev-server\node_modules\mime'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@pnp',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules@pnp\odata\node_modules\tslib'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@pnp\odata\node_modules\tslib'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\esrecurse',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules\esrecurse\node_modules\estraverse'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\esrecurse\node_modules\estraverse'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules@microsoft\sp-webpart-base\node_modules@microsoft\microsoft-graph-client'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@microsoft\sp-webpart-base\node_modules\@microsoft\microsoft-graph-client'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@microsoft\spfx-heft-plugins',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules@microsoft\spfx-heft-plugins\lib\plugins'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@microsoft\spfx-heft-plugins\lib\plugins'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@microsoft',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'PROJECT-PATH\node_modules@microsoft\spfx-heft-plugins\lib\plugins'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@microsoft\spfx-heft-plugins\lib\plugins'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@typescript-eslint\parser',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'PROJECT-PATH\node_modules@typescript-eslint\parser\node_modules@typescript-eslint\experimental-utils'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@typescript-eslint\parser\node_modules\@typescript-eslint\experimental-utils'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@pnp\spfx-controls-react\node_modules',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'PROJECT-PATH\node_modules@pnp\spfx-controls-react\node_modules@microsoft\sp-loader\node_modules\office-ui-fabric-react\lib-amd'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@pnp\spfx-controls-react\node_modules\@microsoft\sp-loader\node_modules\office-ui-fabric-react\lib-amd'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@typescript-eslint',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'PROJECT-PATH\node_modules@typescript-eslint\parser'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@typescript-eslint\parser'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@microsoft\sp-extension-base',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'PROJECT-PATH\node_modules@microsoft\sp-extension-base\node_modules@microsoft\sp-loader'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@microsoft\sp-extension-base\node_modules\@microsoft\sp-loader'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\browser-resolve',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'PROJECT-PATH\node_modules\browser-resolve\node_modules'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\browser-resolve\node_modules'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup 'PROJECT-PATH\node_modules\@microsoft\fast-foundation',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'PROJECT-PATH\node_modules@microsoft\fast-foundation\node_modules@microsoft\tsdoc-config\lib_tests_'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'PROJECT-PATH\node_modules\@microsoft\fast-foundation\node_modules\@microsoft\tsdoc-config\lib\tests'
npm warn cleanup }
npm warn cleanup ]
npm warn cleanup ]
npm error code 1
npm error path PROJECT-PATH\node_modules\node-sass
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js
npm error Building: C:\Program Files\nodejs\node.exe PROJECT-PATH\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm error gyp info it worked if it ends with ok
npm error gyp verb cli [
npm error gyp verb cli 'C:\Program Files\nodejs\node.exe',
npm error gyp verb cli 'PROJECT-PATH\node_modules\node-gyp\bin\node-gyp.js',
npm error gyp verb cli 'rebuild',
npm error gyp verb cli '--verbose',
npm error gyp verb cli '--libsass_ext=',
npm error gyp verb cli '--libsass_cflags=',
npm error gyp verb cli '--libsass_ldflags=',
npm error gyp verb cli '--libsass_library='
npm error gyp verb cli ]
npm error gyp info using [email protected]
npm error gyp info using [email protected] | win32 | x64
npm error gyp verb command rebuild []
npm error gyp verb command clean []
npm error gyp verb clean removing "build" directory
npm error gyp verb command configure []
npm error gyp verb check python checking for Python executable "python2" in the PATH
npm error gyp verb which failed Error: not found: python2
npm error gyp verb which failed at getNotFoundError (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:13:12)
npm error gyp verb which failed at F (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:68:19)
npm error gyp verb which failed at E (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:80:29)
npm error gyp verb which failed at PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:89:16
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\index.js:42:5
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\windows.js:36:5
npm error gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21)
npm error gyp verb which failed python2 Error: not found: python2
npm error gyp verb which failed at getNotFoundError (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:13:12)
npm error gyp verb which failed at F (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:68:19)
npm error gyp verb which failed at E (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:80:29)
npm error gyp verb which failed at PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:89:16
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\index.js:42:5
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\windows.js:36:5
npm error gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21) {
npm error gyp verb which failed code: 'ENOENT'
npm error gyp verb which failed }
npm error gyp verb check python checking for Python executable "python" in the PATH
npm error gyp verb which failed Error: not found: python
npm error gyp verb which failed at getNotFoundError (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:13:12)
npm error gyp verb which failed at F (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:68:19)
npm error gyp verb which failed at E (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:80:29)
npm error gyp verb which failed at PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:89:16
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\index.js:42:5
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\windows.js:36:5
npm error gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21)
npm error gyp verb which failed python Error: not found: python
npm error gyp verb which failed at getNotFoundError (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:13:12)
npm error gyp verb which failed at F (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:68:19)
npm error gyp verb which failed at E (PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:80:29)
npm error gyp verb which failed at PROJECT-PATH\node_modules\node-gyp\node_modules\which\which.js:89:16
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\index.js:42:5
npm error gyp verb which failed at PROJECT-PATH\node_modules\isexe\windows.js:36:5
npm error gyp verb which failed at FSReqCallback.oncomplete (node:fs:202:21) {
npm error gyp verb which failed code: 'ENOENT'
npm error gyp verb which failed }
npm error gyp verb could not find "python". checking python launcher
npm error gyp verb could not find "python". guessing location
npm error gyp verb ensuring that file exists: C:\Python27\python.exe
npm error gyp ERR! configure error
npm error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
npm error gyp ERR! stack at PythonFinder.failNoPython (PROJECT-PATH\node_modules\node-gyp\lib\configure.js:484:19)
npm error gyp ERR! stack at PythonFinder.
Diagnostics
No response
CLI for Microsoft 365 version
10.8.0
nodejs version
18.20.5
Operating system (environment)
Windows
Shell
cmd
cli doctor
No response
Additional Info
No response
Hi @I-BhushanSalunkhe, could you give us some more info, please?
You were able to create an upgrade report and have completed all steps successfully? Did you specify the correct --shell parameter?
You've deleted your old node_modules and package-lock.json file, but npm i gives errors?
Which Node version are you using?
Is it possible to share your package.json file?
@milanholemans, thank you for looking into this issue.
Yes, I was able to generate the upgrade report by executing below command.
m365 spfx project upgrade --toVersion 1.21.1 --output md > upgrade-report.md
Yes, I have deleted node_modules and package-lock.json and received errors for npm install.
I am using Node v22.16.0.
PFA package.json, complete log of npm install and error logs
Project Upgrade - npm install - logs.txt
2025-06-09T08_14_06_166Z-debug-0.log
Glancing quickly over package.json, I can see that @microsoft/sp-module-interfaces for some reason is still on v1.14.0. Could you see if manually changing it to v1.21.1 fixes your issue?
@waldekmastykarz, I have re-executed all the steps given the article with correct version of @microsoft/sp-module-interfaces, but still, I am facing same issue for npm install.
Attaching log and package.json for your reference.
2025-06-12T11_46_05_376Z-debug-0.log
Thank you for the additional information @I-BhushanSalunkhe. To confirm: if you create a brand new v1.21.1 project, it works just fine?
I'm also noticing that you are using spfx-fast-serve-helpers v1.15.4 which is not compatible with the latest SPFx v1.21.1 version. Have you considered removing this dependency or upgrade it?
Thank you, @milanholemans, for sharing your observations! I’ll give it a try by upgrading and removing spfx-fast-serve-helpers, and I’ll let you know how it goes.
@waldekmastykarz, I’m planning to create a brand new project using SPFx version 1.21.1 as well — will share the results once done.
@waldekmastykarz & @milanholemans,
I tried executing npm install after upgrading to the latest version of spfx-fast-serve-helpers (v1.21.1) and also after removing it entirely from package.json, but in both cases, the npm install still fails with the same results.
However, when I created a fresh SPFx project without any third-party or additional packages, everything ran smoothly without any errors.
Thanks for the extra check, @I-BhushanSalunkhe, and your patience. Is there a chance for you to share with us a minimal project setup that we could use to reproduce the issue? It would help us a lot to understand what's failing and why.
Hey @I-BhushanSalunkhe, I tried to simulate your use case but couldn’t reproduce the issue. One thing I did notice in your package.json: I’d recommend removing @microsoft/rush-stack-compiler-3.9, it’s outdated and not needed for current TS version.
Looking at the npm install errors, it seems like SPFx v1.14.0 is still being pulled in. That version requires Node 14, so make sure there are no lingering references to 1.14. Also, double-check that node_modules and package-lock.json are completely removed before reinstalling.
As @waldekmastykarz mentioned, sharing a bit more structure from your project could help pinpoint the issue better.
Hi @Jwaegebaert,
As per my current package.json, the Rush Stack compiler is already set to "@microsoft/rush-stack-compiler-5.3": "0.1.0", which matches the version used in a newly created SPFx project.
Regarding sharing the project structure, since this is client IP, I’ll need more specific details about what exactly you’d like me to share so I can verify internally what’s permissible.
Just to confirm, I’m using Node.js version 22.16.0, and before running npm install, I’ve deleted both the node_modules folder and the package-lock.json file.
Attaching latest package.json for your reference.
I think I can repro it by running the first command from the upgrade report npm un -S office-ui-fabric-react on a vanilla 1.14.0 React web part project. I think the issue is related to a very old dependency in SPFx that's failing installation (when you're uninstalling a package, npm will do an installation if it didn't previously). One way I was able to work around it, was to manually bump all SPFx dependency versions to 1.21.1, after which I could run npm commands just fine. Not ideal, I understand, but it's something beyond our control. Could you please check if this is working for you @I-BhushanSalunkhe?
Thank you, @waldekmastykarz, for your quick response.
Just to confirm my understanding—should we completely skip the upgrade report's instructions and directly upgrade all SPFx dependencies (like @microsoft/sp-core-library, @microsoft/sp-webpart-base, etc.) to 1.21.1 and then run npm install?
Or should we follow the Modify files steps mentioned in the upgrade report but skip only the Execute script block and then proceed to update all SPFx dependencies to 1.21.1, followed by npm install?
Would appreciate your guidance on the correct path forward.
First, manually update all SPFx dependencies to v1.21.1, then run the upgrade script from the report.
Hi @waldekmastykarz,
Apologies for the delayed response.
I’ve followed the steps below to upgrade the SPFx project:
- Downloaded the original solution from the DevOps repository.
- Set Node version to
14.21.23. - Ran
npm install. - Switched Node version to
22.16.0. - Executed the command:
m365 spfx project upgrade --toVersion 1.21.1 --output md > upgrade-report.md - Manually updated SPFx dependencies to version
1.21.1. - Ran the
Execute scriptblock from the upgrade report, followed byModify files. - Ran
npm installagain.
Despite these steps, the output still fails with the same results.
Could you please advise if I might be missing something or if there’s a known issue with this upgrade path?
Have you also tried the following:
- Use Node 22
- Get the solution from source control
- Run
m365 spfx project upgrade --toVersion 1.21.1 --output md > upgrade-report.md - Remove
package-lock.json/npm-shrinkwrap.json - Delete
node_modulesif it exists - Manually update SPFx dependencies to v1.21.1 in package.json
- Run
npm install - Run the script from the update report
The main difference here is not running npm install on the original project and not having node_modules with old packages before running the upgrade script.
I’ve followed the suggested sequence of steps, but unfortunately, I’m still encountering the same issue.
To assist with troubleshooting, I’ve attached the log file generated during the npm install step.
Please let me know if you spot anything unusual or if there’s anything else I should try.
Just a quick question — do I need to update the Rush Stack Compiler version as part of the SPFx upgrade to 1.21.1, before running npm install?
2025-06-23T07_00_14_815Z-debug-0.log
Thanks for the additional information. At this stage, we'd really need a repro project. I tried the steps I proposed on a standard v1.14.0 project and it seemed to work. If it's still failing in your case, then we'd need to be able to reproduce it.
@waldekmastykarz, apologies for the delayed response.
Due to client policy restrictions, I’m unable to share the IP. However, I successfully upgraded the SPFx version from 1.14.0 to 1.21.1 on a vanilla SPFx solution using the HelloWorld web part. The upgrade went through smoothly, though I encountered the following error during execution of the commands gulp serve and gulp bundle --ship:
Error - [lint] Unexpected STDERR output from ESLint:
Oops! Something went wrong! :(
ESLint: 8.57.1
ReferenceError: Cannot read config file: C:\Bhushan Salunkhe\SPFx 14.21.3\.eslintrc.js
Error: require is not defined
at file:///C:/Bhushan%20Salunkhe/SPFx%2014.21.3/.eslintrc.js:1:1
at ModuleJobSync.runSync (node:internal/modules/esm/module_job:400:35)
at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:427:47)
at loadESMFromCJS (node:internal/modules/cjs/loader:1561:24)
at Module._compile (node:internal/modules/cjs/loader:1712:5)
at Object..js (node:internal/modules/cjs/loader:1895:10)
at Module.load (node:internal/modules/cjs/loader:1465:32)
at Function._load (node:internal/modules/cjs/loader:1282:12)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
I’m keen to understand reported issue better and explore possible resolutions. Would it be possible to connect with you in your time zone via Microsoft Teams or any other communication platform you prefer?
The issue might be related to ES Modules vs. Common JS. Have you compared both projects (after upgrade vs. brand new) to understand the differences?
I will definitely compare both projects. However, I’m still uncertain about how to proceed with the original issue raised in this ticket, as I’m not permitted to share the client’s IP due to policy restrictions.
Could you please advise on an alternative approach or any additional information that might help move this forward?
We need to understand what's failing exactly, so we'd need a minimal repro. One way you could go about it is to create a new project that matches your customer's version, and then keep adding changes to it until you can reproduce the issue. You can omit any customer-specific information.
Hi @waldekmastykarz,
We’ve prepared a minimal code base to help reproduce the issue we’re currently facing. Please find the attached ZIP file for your review and troubleshooting.
We would appreciate it if you could take a look and share your observations or suggestions to help us resolve the issue.
Thank you for your continued support.
Thanks for sharing your project, @I-BhushanSalunkhe, makes it easier to dig into the issue.
On my first test, I already spotted a few things that could help:
- Remove the
react-loaderpackage, it’s no longer supported and won’t work with Node 22 - Update
@pnp/spfx-controls-reactto version3.21.0
After making these changes, I got it running on the latest SPFx version. You’ll just need to look for an alternative to react-loader.
Thank you @Jwaegebaert for looking into it. I’ll give it a try and share the output once done.
Hi @Jwaegebaert,
I’ve removed react-loader and updated @pnp/spfx-controls-react to version 3.21.0, as suggested. However, I’m still encountering the same errors while executing the scripts listed under the summary section of the upgrade report.
I’ve attached the complete command prompt logs for your reference.
Could you please share the steps you followed during your upgrade process, along with your package.json file? That would be really helpful in identifying any discrepancies.
@I-BhushanSalunkhe I'd recommend clearing your currently installed modules and starting fresh with Node 22. Then manually update all the versions in package.json. That approach worked best for me.
@I-BhushanSalunkhe any update on this one? Did you had the chance to recheck @Jwaegebaert suggestion?
