TypeError: Failed to fetch dynamically imported module after upgrading to v9.3.5

Bug report

Congratulations on the new release! Just upgraded to 9.3.5 from 9.1.0 and we’ve run into TypeError: Failed to fetch dynamically imported module http://localhost:8081/_next/static/runtime/dev/noop

Describe the bug

The bug is not breaking our build but is showing in the browser console.

To Reproduce

yarn upgrade next@latest yarn build next dist --p 8081

Expected behavior

Not having errors in the console

System information

• OS: macOS Catalina 10.15.3
• Browser: Chrome 80
• Version of Next.js: 9.3.5
• Version of Node.js: 10.17.0
• Version of Yarn: 1.22.4

Aditional Information

Here are some of our dependencies that I think are interacting with next

    "@types/react": "16.9.1",
    "@types/react-dom": "^16.9.0",
    "@types/webpack": "^4.4.34",
    "@zeit/next-css": "^1.0.1",
    "@zeit/next-mdx": "^1.2.0",
    "babel-loader": "^8.0.6",
    "concurrently": "^4.1.1",
    "copy-webpack-plugin": "^5.1.1",
    "csstype": "2",
    "http-server": "^0.11.1",
    "next": "^9.1.0",
    "next-images": "^1.1.0",
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "react-helmet": "^5.2.1",
    "webpack": "^4.17.1",
    "webpack-cli": "^3.1.0"
  },
  "resolutions": {
    "react": "16.9.0"
  },
  "peerDependencies": {
    "react": ">= 16.8.0 < 17",
    "react-dom": ">= 16.8.0 < 17",
  },

[timneutkens]

Guess this can be closed since it’s not an issue directly in Next.js?

[ijjk]

It sounds like the security alert you may be referencing is the one for Regular Expression Denial of Service in acorn. This alert is triggered as dangerous since the security alerts don’t take into account where the code is being used. In this case acorn is used to process code you have added to the project. acorn is also only used during build time and should not be included in resulting build bundles at all.

It is best to not try to manually resolve packages like this and let us maintain the correct versions of packages unless you are sure the versions are compatible with all the packages that rely on it and it doesn’t make sense for the package to be updated upstream also. In this case it does not appear to be compatible with all installed packages causing the above error