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.

Build Failure : ReferenceError: namespae is not defined

See original GitHub issue

I pulled the latest code and tried building it, Can someone please tell me why it is failing?

Loading "eslint.js" tasks...ERROR
>> ReferenceError: namespae is not defined

C:\web-ext>npm run build

> web-ext@1.6.0 build C:\web-ext
> grunt build

Loading "eslint.js" tasks...ERROR
>> ReferenceError: namespae is not defined

Running "clean:dist" (clean) task
>> 1 path cleaned.

Running "webpack:build" (webpack) task
Version: webpack 1.14.0

ERROR in namespae is not defined
Warning: Task "webpack:build" failed. Use --force to continue.

Aborted due to warnings.

npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\aniket\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
npm ERR! node v4.4.7
npm ERR! npm  v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! web-ext@1.6.0 build: `grunt build`
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the web-ext@1.6.0 build script 'grunt build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the web-ext package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     grunt build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs web-ext
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls web-ext
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\web-ext\npm-debug.log

Issue Analytics

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

Top GitHub Comments

1reaction

shubhekshacommented, Dec 16, 2016

What version of node and npm are you using? Edit: It’ll be easier to debug if you use the issue template while filing bugs. 😄

0reactions

kumar303commented, Dec 16, 2016

Thanks for submitting a bug. Let us know if you run into any other problems. In npm 3+, all deps are flattened which means namespae is probably a dep of a dep (… of a dep).

Top Results From Across the Web

Typescript ReferenceError: Namespace is not defined

Ex. I'm getting a runtime error saying: Typescript ReferenceError: Namespace is not defined. Do you have any idea how to solve this? The...

error: Uncaught ReferenceError: namespace is not defined ...

I looked around the internet and found a solid looking solution for creating a namespace. Currently my code looks something like this: class...

Internal namespace modules giving not defined errors. #246

Everything compiles and bundles fine, but at runtime I get an error that A is not defined. Looking at the bundled output, I...

Documentation - Namespaces and Modules - TypeScript

This post outlines the various ways to organize your code using modules and namespaces in TypeScript. We'll also go over some advanced topics...

Angular - ReferenceError x is not defined - Web - v5 - IMG.LY

The ReferenceError: x is not defined error message will appear if you use the optimization option in the angular.json . The additional uglification...