You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
Can we update to [email protected] in the 18.2.x branch? It fixes webpack/webpack#19498, which is a type error that is occuring since a recent @types/node version.
I saw that webpack was recently updated on main #30260, but 18.2.x is still using an older webpack version. Is it planned to update webpack on 18.2.x in this case to fix the type error?
Minimal Reproduction
I get the error when building a storybook app based on Angular 18.2. Please let me know if providing a reproduction is helpful, then I'll try to set up a public repro.
Exception or Error
node_modules/webpack/types.d.ts:14856:15 - error TS2417: Class static side 'typeof WebpackError' incorrectly extends base class static side '{ readonly prototype: Error; captureStackTrace(targetObject: object, constructorOpt?: Function | undefined): void; prepareStackTrace(err: Error, stackTraces: CallSite[]): any; stackTraceLimit: number; }'.
Types of property 'prepareStackTrace' are incompatible.
Type '((err: Error, stackTraces: CallSite[]) => any) | undefined' is not assignable to type '(err: Error, stackTraces: CallSite[]) => any'.
Type 'undefined' is not assignable to type '(err: Error, stackTraces: CallSite[]) => any'.
14856 declare class WebpackError extends Error {
~~~~~~~~~~~~
Although this error is caused by a third-party change and falls under the LTS policy, updating Webpack in an LTS release is considerably risky. Especially since there are safer alternatives. You can resolve the issue by enabling skipLibCheck, which is also the recommended approach by TypeScript, or by pinning the @types/node package.
Also, I'm not sure why Webpack is being included in your compilation generally, that shouldn't be the case.
Command
build
Is this a regression?
The previous version in which this bug was not present was
No response
Description
Can we update to [email protected] in the 18.2.x branch? It fixes webpack/webpack#19498, which is a type error that is occuring since a recent @types/node version.
I saw that webpack was recently updated on main #30260, but 18.2.x is still using an older webpack version. Is it planned to update webpack on 18.2.x in this case to fix the type error?
Minimal Reproduction
I get the error when building a storybook app based on Angular 18.2. Please let me know if providing a reproduction is helpful, then I'll try to set up a public repro.
Exception or Error
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: