question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Uncaught ReferenceError" webpack compatibility

See original GitHub issue

that’s not a sheet-router issue

https://github.com/yoshuawuyts/sheet-router/issues/28

node v4.4.7 (npm v2.15.8) webpack 1.13

{
  "name": "webpack-choo-testfield",
  "version": "1.0.0",
  "description": "",
  "main": "./src/loader.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "dev": "webpack-dev-server"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "autoprefixer": "^6.3.7",
    "babel-core": "^6.10.4",
    "babel-loader": "^6.2.4",
    "babel-plugin-transform-runtime": "^6.9.0",
    "babel-preset-es2015": "^6.9.0",
    "babel-preset-stage-0": "^6.5.0",
    "coffee-loader": "^0.7.2",
    "coffee-script": "^1.10.0",
    "css-loader": "^0.23.1",
    "exports-loader": "^0.6.3",
    "extract-text-webpack-plugin": "^1.0.1",
    "handlebars": "^4.0.5",
    "handlebars-loader": "^1.3.0",
    "html-webpack-plugin": "^2.22.0",
    "nib": "^1.1.0",
    "postcss-loader": "^0.9.1",
    "postcss-short": "^1.4.0",
    "raw-loader": "^0.5.1",
    "style-loader": "^0.13.1",
    "stylus": "^0.54.5",
    "stylus-loader": "^2.1.1",
    "webpack": "^1.13.1",
    "webpack-dev-server": "^1.14.1"
  },
  "dependencies": {
    "babel-polyfill": "^6.9.1",
    "babel-runtime": "^6.9.2",
    "choo": "^3.0.2",
    "faker": "^3.1.0",
    "lodash": "^4.13.1",
    "moment": "^2.14.1"
  }
}

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
drewschraufcommented, Jul 12, 2016

FWIW, I had a issue running choo with webpack when the devtool was set to eval. I changed it to source-map and things started working fine.

0reactions
crapthingscommented, Jul 13, 2016

i’ve tested, that is a chrome bug

https://github.com/webpack/webpack/issues/2756#issuecomment-232272889

safari works with cheap-eval

Read more comments on GitHub >

github_iconTop Results From Across the Web

Webpack 5 - Uncaught ReferenceError: process is not defined
Try to use frontend-compatible modules whenever possible. It's possible to manually add a polyfill for a node.js core module. An error message ...
Read more >
When I run the dev server, I got an error 'Uncaught ... - GitHub
I found out that externals: [nodeExternals()] is compatible with mode: 'production' and target: 'web' . So, why not just exclude the mode ...
Read more >
uncaught referenceerror: $ is not defined webpack - You.com
Try to use frontend-compatible modules whenever possible. It's possible to manually add a polyfill for a node.js core module. An error message will...
Read more >
To v5 from v4 - webpack
Test webpack 5 compatibility ... Try to set the following options in your webpack 4 configuration and check if build still works correctly....
Read more >
Module Bundler in JavaScript – How to Use Webpack
... and dependencies into a single browser-compatible JavaScript file. ... error that says Uncaught ReferenceError: require is not defined .
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found