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.

Error: Node's Buffer() not available

See original GitHub issue

Hi,

I am developing an single page app with vue-cli webpack-simple. The only dependencies are firebase components and this library. The Chrome console is showing the error below:

Uncaught Error: Node's Buffer() not available
    at Object.eval (eval at <anonymous> (build.js:1322), <anonymous>:53:11)
    at eval (eval at <anonymous> (build.js:1322), <anonymous>:129:30)
    at Object.<anonymous> (build.js:1322)
    at __webpack_require__ (build.js:658)
    at fn (build.js:86)
    at eval (eval at <anonymous> (build.js:1239), <anonymous>:8:63)
    at Object.<anonymous> (build.js:1239)
    at __webpack_require__ (build.js:658)
    at fn (build.js:86)
    at eval (eval at <anonymous> (build.js:1746), <anonymous>:7:3)

Issue Analytics

State:
Created 6 years ago
Comments:27

Top GitHub Comments

23reactions

TimvdLippecommented, Sep 6, 2017

Reverting to 0.2.27 seems to fix this issue. The 0.2.28 release seems to explicitly mention it broke the browser version. Not sure why this was done in a patch version 🤔

1reaction

westlakemcommented, Feb 19, 2018

@bufface @gabor @leonardo-sj I agree, the issue should not be closed as this breaks the ability to upgrade. Issues should be made for the most current version of the tool, and left open until the most recent version of the tool doesn’t have the issue anymore.

Top Results From Across the Web

Buffer not found in Node.JS browser code - Stack Overflow

js in my browser code, it prints the Buffer variable. However, I still get the same error ( ReferenceError: Buffer is not defined...

Error: "Node not available"

Since i've updated Node-Red, NVM and NodeJS today i'm getting an Errormessage on all my existing Flows: "Node not available".

Process | Node.js v19.3.0 Documentation

The process.abort() method causes the Node.js process to exit immediately and generate a core file. This feature is not available in Worker threads ......

How to polyfill Buffer with Webpack 5 - viglucci.io

How to fix 'buffer is not defined' error and polyfill the Node.js Buffer ... There are sometimes comparable APIs available in the browser ......

Top 10 Most Common Node.js Developer Mistakes - Toptal

Being careful is all it takes to avoid this Node.js error. Some Node.js developers ... writeHead(404) return res.end() } var buf = new...