Latest version of Angular installs tapable 2.2.0 which conflicts with storybook 1.1.3 requirement
See original GitHub issueDescribe the bug After installing storybook into a clean angular 11.0.4 project, tapable throws a number of errors while compiling typescript.
To Reproduce
- Create a fresh Angular 11.0.4 project.
- Init storybook.
- Run tsc.
Expected behavior tsc compiles without errors
Screenshots
Code snippets results:
node_modules/@types/webpack/index.d.ts:32:3 - error TS2305: Module '"../../tapable/tapable"' has no exported member 'Tapable'.
32 Tapable,
~~~~~~~
node_modules/@types/webpack/index.d.ts:1062:23 - error TS2707: Generic type 'SyncWaterfallHook<T, AdditionalOptions>' requires between 1 and 2 type arguments.
1062 resolver: SyncWaterfallHook;
~~~~~~~~~~~~~~~~~
and many more
System
Environment Info:
System:
OS: macOS 11.0.1
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Binaries:
Node: 12.15.0 - ~/.nvm/versions/node/v12.15.0/bin/node
Yarn: 1.22.10 - ~/.nvm/versions/node/v12.15.0/bin/yarn
npm: 6.14.9 - ~/.nvm/versions/node/v12.15.0/bin/npm
Browsers:
Chrome: 87.0.4280.88
Edge: 87.0.664.60
Firefox: 80.0.1
Safari: 14.0.1
npmPackages:
@storybook/addon-actions: ^6.1.11 => 6.1.11
@storybook/addon-essentials: ^6.1.11 => 6.1.11
@storybook/addon-links: ^6.1.11 => 6.1.11
@storybook/angular: ^6.1.11 => 6.1.11
Additional context
I was able to resolve by forcing tsc 1.1.3, but unfortunately that will likely cause issues with angular dev kit which transiently requires 2.2.0.
angular-to-do@0.0.0
βββ¬ @angular-devkit/build-angular@0.1100.4
β βββ¬ @ngtools/webpack@11.0.4
β β βββ¬ enhanced-resolve@5.3.1
β β βββ tapable@2.2.0
β βββ¬ webpack@4.44.2
β βββ¬ enhanced-resolve@4.3.0
β β βββ tapable@1.1.3 deduped
β βββ tapable@1.1.3
βββ¬ @storybook/angular@6.1.11
βββ¬ @storybook/core@6.1.11
β βββ¬ html-webpack-plugin@4.5.0
β β βββ tapable@1.1.3
β βββ¬ react-dev-utils@10.2.1
β βββ¬ fork-ts-checker-webpack-plugin@3.1.1
β βββ tapable@1.1.3
βββ¬ fork-ts-checker-webpack-plugin@4.1.6
β βββ tapable@1.1.3
βββ¬ ts-loader@6.2.2
β βββ¬ enhanced-resolve@4.3.0
β βββ tapable@1.1.3
βββ¬ tsconfig-paths-webpack-plugin@3.3.0
βββ¬ enhanced-resolve@4.3.0
βββ tapable@1.1.3
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:14 (2 by maintainers)
Top Results From Across the Web
Problem with npm install - Could not resolve dependency. Is ...
I want to create a regular situation without this issue. I want to launch only npm I without forcing it. How can I...
Read more >Storybook for Angular tutorial
It helps you build UI components isolated from the business logic and context of your app. This edition of the Intro to Storybook...
Read more >@storybook/react-native-server | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >Open Source Used In CloudCenter SA 5.2.4 - Cisco
1.33.1 Available under license. 1.34 spring-cloud-starter-netflix-zuul 1.4.5.RELEASE. 1.34.1 Available under license. 1.35 angular-sanitize 1.6.5.
Read more >Releases - CodeceptJS
Added TS types for helpers config: Playwright; Puppeteer; WebDriver; REST. Added TypeScript option for installation via codeceptjs init to initialize new ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry @Imp0ssible but this a problem of StoryBook. Enabling skipLibCheck is not a valid solution for many projects.
itβs not storybook issue
"compilerOptions": { "skipLibCheck": true }