Next.js: TypeError: Cannot read property 'tap' of undefined

Created on 30 Nov 2018  路  10Comments  路  Source: vercel/next.js

Bug report

Describe the bug

yarn build :

Compiling client /Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/webpack/lib/ProgressPlugin.js:205 **compilation.hooks.addEntry.tap("ProgressPlugin", entryAdd);** ^ TypeError: Cannot read property 'tap' of undefined at compiler.hooks.compilation.tap.compilation (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/webpack/lib/ProgressPlugin.js:205:32) at SyncHook.eval [as call] (eval at create (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:9:1) at SyncHook.lazyCompileHook (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/tapable/lib/Hook.js:154:20) at Compiler.newCompilation (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/next/node_modules/webpack/lib/Compiler.js:498:26) at hooks.beforeCompile.callAsync.err (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/next/node_modules/webpack/lib/Compiler.js:534:29) at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/tapable/lib/HookCodeFactory.js:32:10), <anonymous>:6:1) at AsyncSeriesHook.lazyCompileHook (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/tapable/lib/Hook.js:154:20) at Compiler.compile (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/next/node_modules/webpack/lib/Compiler.js:529:28) at readRecords.err (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/next/node_modules/webpack/lib/Compiler.js:268:11) at Array.inputFileSystem.stat.err (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/next/node_modules/webpack/lib/Compiler.js:401:20) at Storage.finished (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16) at provider (/Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9) at /Users/helabenkhalfallah/Desktop/github_workspace/news_kit_frontend/node_modules/graceful-fs/polyfills.js:282:31 at FSReqWrap.oncomplete (fs.js:170:21)

My project :
https://github.com/helabenkhalfallah/news_kit_frontend

Thanks :)

Most helpful comment

Try removing "webpack" from package.json, remove package-lock.json and node_modules directory. Then reinstall the packages with npm install

All 10 comments

Not sure what to do with this, it sounds like you're on an old version of webpack or something.

Try deleting your node_modules and package-lock.json file and do npm install again. I get tap errors when switching back and forth between modules with different dependency versions of webpack. Something isn't getting cleaned up right with npm.

Try removing "webpack" from package.json, remove package-lock.json and node_modules directory. Then reinstall the packages with npm install

I hate webpack, im trying to deploy my app to heroku and isnt working, locally it does work , when i remove all node_modules, and install packages and then [email protected] , but in heroku it doesnt it always give same error

Error: Cannot find module 'webpack/lib/RequestShortener'

error also on Now, zeit, idk where to deploy my application, i think i will have to use my application static and make it a way to load dynamic posts.

I removed all references to webpack from package.json, rm -rf node_modules package-lock.json and npm i, and still get this error. Next 7.0.2

I've also run into Cannot read property 'tap' of undefined.

I need to install webpack for react-styleguidist, but it seems if the version doesn't match the one Next is using this error occurs. I solved this by specifically installing the same webpack version Next requires.

If you use Yarn you might be able to solve this with its selective dependency resolutions, but haven't tried that myself.

I solved by removing node_modules, removing any reference to webpack, restarting the computer and running npm i (note that without the restart, it didn't work). This is not an easy bug to fix it seems

This error occurred when I tried to use Next 7.0.2 with Webpack 4.27.1

I had to downgrade webpack version to 4.20.2 for this error to go away.

@renjithgr That's because Next 7.0.2 is powered by Webpack 4.20.2 under the hood.

If you're going to use Webpack in addition to other libraries that use Webpack as a dependency, it is probably a good idea to be consistent (like with Storybook).

I.e. some package.json

    "next": "7.0.2",
    "webpack": "4.20.2",

Upgrade to major/minor versions wisely.

Sometimes npm install doesn't install firebase so you have to do yarn install.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

YarivGilad picture YarivGilad  路  3Comments

sospedra picture sospedra  路  3Comments

timneutkens picture timneutkens  路  3Comments

irrigator picture irrigator  路  3Comments

flybayer picture flybayer  路  3Comments