Uncaught ReferenceError: dll is not defined #5702

Jero786 · 2018-11-19T11:05:29Z

Bug report

The error Uncaught ReferenceError: dll_xxxxxx is not defined it happens a soon as you create a empty project and open it. Please take a look the following demo project.

It does only happening in Chrome! in FF it's works fine.

MacOs Sierra: 10.13.6
Chrome Version: 70.0.3538.102
Node: v10.10.0
NPM: v6.4.1

Package dependencies:

 "@zeit/next-sass": "^1.0.2-canary.0",
    "babel-polyfill": "^6.26.0",
    "classnames": "^2.2.6",
    "cross-fetch": "^2.2.2",
    "express": "^4.16.4",
    "fs": "0.0.1-security",
    "immutable": "^3.8.2",
    "lodash": "^4.17.10",
    "next": "^7.0.2-canary.21",
    "next-redux-wrapper": "^2.0.0",
    "node-sass": "4.9.4",
    "prop-types": "^15.6.2",
    "react": "^16.4.2",
    "react-dom": "^16.4.2",
    "react-notification-system": "^0.2.17",
    "react-redux": "^5.0.7",
    "redux": "^4.0.0",
    "redux-devtools-extension": "^2.13.5",
    "redux-immutable": "^4.0.0",
    "redux-thunk": "^2.3.0"

my dev dependencies:

"devDependencies": {
    "babel-core": "7.0.0-bridge.0",
    "babel-eslint": "^8.2.6",
    "babel-jest": "22.4.3",
    "babel-plugin-module-resolver": "^3.1.1",
    "chai": "^4.1.2",
    "enzyme": "3.2.0",
    "enzyme-adapter-react-16": "1.5.0",
    "eslint": "^4.19.1",
    "eslint-config-airbnb": "^17.0.0",
    "eslint-plugin-import": "^2.13.0",
    "eslint-plugin-jsx-a11y": "^6.1.1",
    "eslint-plugin-react": "^7.10.0",
    "husky": "^0.14.3",
    "jest": "22.0.1",
    "lint-staged": "^7.3.0",
    "prettier-eslint": "^8.8.2",
    "react-addons-test-utils": "15.6.2",
    "react-test-renderer": "16.2.0",
    "sinon": "^6.1.5",
    "superagent": "^4.0.0-beta.5",
    "supertest": "^3.3.0"
  }

Expected behavior

Should not show any message error.

Screenshots

Additional context

This bug was closed but it's still there and I change the name of the bug in order to be more searchable.

The text was updated successfully, but these errors were encountered:

timneutkens · 2018-11-19T11:50:44Z

Please provide a full reproduction. I still can't reproduce.

PrimarchAlpharius · 2018-11-20T12:09:59Z

Can confirm the bug, reverting to v7.0.1 solves the problem for me

timneutkens · 2018-11-20T12:45:21Z

Please provide a full reproduction. I still can't reproduce.

I keep repeating myself in these issues 😢

It's really hard to look into or fix anything without a full reproduction of this issue.

Jero786 · 2018-11-20T13:05:25Z

@timneutkens if you just clone the project that I sent, and write npm install && npm run and then open a Chrome it does happen. Again for me only in chrome. (Version 70.0.3538.102 (Official Build) (64-bit)) also I try to update the browser to version Version 70.0.3538.110 (Official Build) (64-bit) and nothing... just the same. The project it's broken. You don't able to trigger any action, and also dont redirect to anyware. And in FF, the route path '/' keep loading forever. I'm very sad for this bug, I don't know what more to try. I'm using NextJS for a production application and after this bug that I faced since 2 weeks ago, I don't know I will need to move on to other vanilla Webpack+react+redux project. :(

Jero786 · 2018-11-20T13:14:57Z

Can confirm the bug, reverting to v7.0.1 solves the problem for me

@PrimarchAlpharius for me it doesn't work :(

timneutkens · 2018-11-20T13:20:56Z

Just tried the repo, which is a Next.js app with one page, meaning it's the equivalent of our test suites, and had no issue at all. I'm on chrome 70.0.3538.102.

davscro · 2018-11-20T15:28:16Z

We are experiencing the same issue. Will try to figure out what's happening there.

davscro · 2018-11-21T08:17:03Z

...also while I am getting above error in chrome console in the same time I see in node console

TypeError: Cannot read property 'finished' of undefined
    at HotReloader._callee2$ (/node_modules/next/dist/server/hot-reloader.js:276:34)
    at tryCatch (/node_modules/@babel/runtime-corejs2/node_modules/regenerator-runtime/runtime.js:62:40)
    at Generator.invoke [as _invoke] (/node_modules/@babel/runtime-corejs2/node_modules/regenerator-runtime/runtime.js:288:22)
    at Generator.prototype.(anonymous function) [as next] (/node_modules/@babel/runtime-corejs2/node_modules/regenerator-runtime/runtime.js:114:21)
    at asyncGeneratorStep (/node_modules/@babel/runtime-corejs2/helpers/asyncToGenerator.js:5:24)
    at _next (/node_modules/@babel/runtime-corejs2/helpers/asyncToGenerator.js:27:9)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:182:7)

I am not sure whether this one is connected 🤔

Jero786 · 2018-11-26T08:25:36Z

I read out there a workaround that seems like fix this problem, could you try guys if that works for you as well?

just add in their .eslintrc

...
"rules": {
...
		"no-console": 1,
...
}
...

djhi · 2018-12-09T13:00:04Z

I reproduced this issue when trying to install both [email protected] and @material-ui/[email protected] which has a peer dependency on [email protected]. When removing @material-ui/[email protected], the issue disappeared so I suspected there were multiple versions of react conflicting.

Adding a resolution key in my package.json for react and react-dom targetting the version I want solved the issue

timneutkens · 2018-12-31T13:19:56Z

So the issue could be react being shipped with a dependency you install 🤔

davidcraig · 2019-03-17T18:26:56Z

I am also getting this error today on a fresh NextJS build - it only happens on localhost (does not happen once the project is deployed) - I am developing on a Windows machine at the minute, perhaps issue is an edge case with webpack on windows node?

Console warning is present in firefox and chrome.

external "dll_513dd14659e539e0c36c":1 Uncaught ReferenceError: dll_513dd14659e539e0c36c is not defined
    at Object.dll-reference dll_513dd14659e539e0c36c (external "dll_513dd14659e539e0c36c":1)
    at __webpack_require__ (bootstrap:788)
    at fn (bootstrap:149)
    at Object../node_modules/react/index.js?79ad (index.js from dll-reference dll_513dd14659e539e0c36c:1)
    at __webpack_require__ (bootstrap:788)
    at fn (bootstrap:149)
    at Object../node_modules/next/dist/client/index.js (index.js:35)
    at __webpack_require__ (bootstrap:788)
    at fn (bootstrap:149)
    at Object../node_modules/next/dist/client/next-dev.js (next-dev.js:23)
dll-reference dll_513dd14659e539e0c36c @ external "dll_513dd14659e539e0c36c":1
__webpack_require__ @ bootstrap:788
fn @ bootstrap:149
./node_modules/react/index.js?79ad @ index.js from dll-reference dll_513dd14659e539e0c36c:1
__webpack_require__ @ bootstrap:788
fn @ bootstrap:149
./node_modules/next/dist/client/index.js @ index.js:35
__webpack_require__ @ bootstrap:788
fn @ bootstrap:149
./node_modules/next/dist/client/next-dev.js @ next-dev.js:23
__webpack_require__ @ bootstrap:788
fn @ bootstrap:149
0 @ module.js:22
__webpack_require__ @ bootstrap:788
checkDeferredModules @ bootstrap:45
webpackJsonpCallback @ bootstrap:32
(anonymous) @ main.js?ts=1552845440736:1

Package.json deps

"dependencies": {
    "@fortawesome/fontawesome-svg-core": "^1.2.15",
    "@fortawesome/free-solid-svg-icons": "^5.7.2",
    "@fortawesome/react-fontawesome": "^0.1.4",
    "@zeit/next-sass": "^1.0.1",
    "bulma": "^0.7.4",
    "next": "^8.0.3",
    "node-sass": "^4.11.0",
    "react": "^16.8.4",
    "react-dom": "^16.8.4"
  },

matiascaputti · 2019-03-30T00:20:49Z

Same happening to me, still not fixed on latests versions.

roelvan · 2019-04-02T05:05:56Z

Just had the same error on "next": "^8.0.4".

vamshikilari · 2019-04-15T11:33:07Z

Same issue! Did anyone find a solution?

aguilarm · 2019-04-17T20:52:00Z

Not sure 100% how to repro what I just did to get this error to show up, but stopping my next dev process and re-installing my node dependencies before restarting next resolved for me. Seems like it could be related to not having certain dependencies next needs at runtime, or yanking them out with npm uninstall or yarn remove while next is still running the dev/webpack process.

I had it happen as a result of a pretty large refactor and haven't been able to repro it however. I imagine most of ya'll could fix this by rm -rf ./node_modules && npm install if I'm correct here. Could explain why @davidcraig's case breaks only locally.

scottie-schneider · 2019-05-04T19:55:26Z

Same error with Next.JS Build. @aguilarm 's solution worked, I npm install'd again, restarted server.

juliosilvacwb · 2019-06-14T18:53:04Z

I stopped my server, running 'npm install' and restart the server, after it the problem disappear.

kabyanil · 2019-08-04T19:21:26Z

I am running nextjs with express as backend. My nextjs runs on localhost:3000 and express runs on localhost:3001. Often times when I change my code, the page doesn't refresh. When I manually refresh, it shows the 404 not found page and Uncaught ReferenceError: dll is not defined in the console. I have to manually run npm run dev and refresh. This is time-consuming. It would be great if somebody shares a solution.

tshazli · 2019-09-13T01:39:10Z

I get this issue but on windows OS AND when the project folder is in a deep path. In essence, I think the issue is related to accessing webpack cache files with long path (longer than 260 chars) which fails the process accessing it.

Try moving your project folder to a shorter path and see if you get this issue so you can verify my theory.

konsumer · 2019-11-04T22:20:05Z

It was not at all clear to me, from the error message, but in my case I had multiple next apps running in a parent now app, and the issues was assetPrefix needs to point to the subdir's location. I tried clearing out things and re-running npm i, both at the top-level and in subdirs and it had issues. I ended up finding #257 and solved my problem in the sub-app's next.config.js:

module.exports = {
  assetPrefix: '/store/'
}

IAmNatch · 2020-02-17T03:25:13Z

In my case, I stopped my server, rm -rf node_modules, npm install, and restarted my server. All was back to normal.

I believe it was caused when I "npm installed" while running the dev server, as mentioned above.

lucasgerard · 2020-05-13T11:24:33Z

I'm having the same issue on version 9.4, and @aguilarm solution to rm -rf node_modules & yarn install did not work for me.

comxd · 2020-06-29T23:48:24Z

@lucasgerard Use &&, not single &.

If cleaning the node_modules not working and you work at localhost:3000 on multiple projects, you need to clear your browser cache/application cache/services workers.

A simple way to full clear all caches for a domain/website (Chrome dev tools):

matiascaputti · 2020-06-29T23:53:50Z

I fixed the problem by forcing service workers to update the site, as they were caching files generating the dll is not defined error.

if ('serviceWorker' in navigator) {
   window.addEventListener('load', function() {
       navigator.serviceWorker.getRegistrations().then(registrations => {
           for(let registration of registrations) {
               registration.unregister().then(bool => {console.log('unregister: ', bool);});
               }
               window.location.reload();
       });
   });
 }

Another approach could be -as @comxd said- unregistering service workers from your browser with the Unregister service workers to force them update cached files.

DaveKnifeman · 2020-07-10T07:49:42Z

@comxd Clearing the browser data worked for me! Thanks!

lazlojuly · 2020-07-13T19:05:21Z

I had a similar issue in local development and running rm -rf .next/cache has resolved it.

timneutkens · 2020-07-13T21:17:12Z

Can you try latest Next.js, the dll plugin was removed

KeitelDOG · 2020-07-17T22:10:51Z

I just experienced it, while setting up Material UI & Co, did not have to delete my Browser Data for localhost

On Chrome Browser:

Open "Dev Tools"
Select the "Network" tab
Check the "Disable Cache"

This will force refresh all the page assets and it should work

uqurtosun · 2020-08-14T09:52:04Z

Don't use : npm start
Do use : npm run dev

Lwdthe1 · 2021-10-26T17:05:18Z

@KeitelDOG's answer worked perfectly while the others didn't do the trick this time

balazsorban44 · 2022-01-27T14:05:52Z

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

timneutkens added the please add a complete reproduction The issue lacks information for further investigation label Nov 20, 2018

timneutkens closed this as completed Dec 31, 2018

jamesmosier mentioned this issue Apr 30, 2020

Uncaught ReferenceError: dll_xxxxxxx is not defined #12340

Closed

vercel locked as resolved and limited conversation to collaborators Jan 27, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uncaught ReferenceError: dll is not defined #5702

Uncaught ReferenceError: dll is not defined #5702

Jero786 commented Nov 19, 2018

timneutkens commented Nov 19, 2018

PrimarchAlpharius commented Nov 20, 2018

timneutkens commented Nov 20, 2018

Jero786 commented Nov 20, 2018 •

edited

Loading

Jero786 commented Nov 20, 2018 •

edited

Loading

timneutkens commented Nov 20, 2018

davscro commented Nov 20, 2018

davscro commented Nov 21, 2018

Jero786 commented Nov 26, 2018

djhi commented Dec 9, 2018

timneutkens commented Dec 31, 2018

davidcraig commented Mar 17, 2019

matiascaputti commented Mar 30, 2019

roelvan commented Apr 2, 2019

vamshikilari commented Apr 15, 2019

aguilarm commented Apr 17, 2019

scottie-schneider commented May 4, 2019

juliosilvacwb commented Jun 14, 2019

kabyanil commented Aug 4, 2019

tshazli commented Sep 13, 2019

konsumer commented Nov 4, 2019

IAmNatch commented Feb 17, 2020

lucasgerard commented May 13, 2020 •

edited

Loading

comxd commented Jun 29, 2020 •

edited

Loading

matiascaputti commented Jun 29, 2020

DaveKnifeman commented Jul 10, 2020

lazlojuly commented Jul 13, 2020 •

edited

Loading

timneutkens commented Jul 13, 2020

KeitelDOG commented Jul 17, 2020

uqurtosun commented Aug 14, 2020

Lwdthe1 commented Oct 26, 2021

balazsorban44 commented Jan 27, 2022

Uncaught ReferenceError: dll is not defined #5702

Uncaught ReferenceError: dll is not defined #5702

Comments

Jero786 commented Nov 19, 2018

Bug report

Expected behavior

Screenshots

Additional context

timneutkens commented Nov 19, 2018

PrimarchAlpharius commented Nov 20, 2018

timneutkens commented Nov 20, 2018

Jero786 commented Nov 20, 2018 • edited Loading

Jero786 commented Nov 20, 2018 • edited Loading

timneutkens commented Nov 20, 2018

davscro commented Nov 20, 2018

davscro commented Nov 21, 2018

Jero786 commented Nov 26, 2018

djhi commented Dec 9, 2018

timneutkens commented Dec 31, 2018

davidcraig commented Mar 17, 2019

matiascaputti commented Mar 30, 2019

roelvan commented Apr 2, 2019

vamshikilari commented Apr 15, 2019

aguilarm commented Apr 17, 2019

scottie-schneider commented May 4, 2019

juliosilvacwb commented Jun 14, 2019

kabyanil commented Aug 4, 2019

tshazli commented Sep 13, 2019

konsumer commented Nov 4, 2019

IAmNatch commented Feb 17, 2020

lucasgerard commented May 13, 2020 • edited Loading

comxd commented Jun 29, 2020 • edited Loading

matiascaputti commented Jun 29, 2020

DaveKnifeman commented Jul 10, 2020

lazlojuly commented Jul 13, 2020 • edited Loading

timneutkens commented Jul 13, 2020

KeitelDOG commented Jul 17, 2020

uqurtosun commented Aug 14, 2020

Lwdthe1 commented Oct 26, 2021

balazsorban44 commented Jan 27, 2022

Jero786 commented Nov 20, 2018 •

edited

Loading

Jero786 commented Nov 20, 2018 •

edited

Loading

lucasgerard commented May 13, 2020 •

edited

Loading

comxd commented Jun 29, 2020 •

edited

Loading

lazlojuly commented Jul 13, 2020 •

edited

Loading