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.

C:/Program Files/shaka-player/demo/cast_receiver/receiver_app.js:19: ERROR - required "goog.asserts" namespace never provided

See original GitHub issue

Have you read the FAQ and checked for duplicate open issues?: Yes What version of Shaka Player are you using?: https://github.com/google/shaka-player.git commit 2924d906f59e503900b6b6adfa368e422917b61c (HEAD -> master, origin/master, origin/HEAD)

Can you reproduce the issue with our latest release version?: Yes

Can you reproduce the issue with the latest code from master?: Yes

Are you using the demo app or your own custom app?: Demo

If custom app, can you reproduce the issue using our demo app?: N/A

What browser and OS are you using?: Chrome, Windows 10 Pro version 1803 build 17134.472

What are the manifest and license server URIs?:

N/A

What did you do? C:\Program Files\shaka-player>python build\all.py [INFO] Generating Closure dependencies… npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated boom@4.3.1: This version is no longer maintained. Please upgrade to the latest version. npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130 npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated hoek@2.16.3: This version is no longer maintained. Please upgrade to the latest version. npm WARN deprecated boom@2.10.1: This version is no longer maintained. Please upgrade to the latest version. npm WARN deprecated cryptiles@2.0.5: This version is no longer maintained. Please upgrade to the latest version. npm WARN prepublish-on-install As of npm@5, prepublish scripts are deprecated. npm WARN prepublish-on-install Use prepare for build steps and prepublishOnly for upload-only. npm WARN prepublish-on-install See the deprecation note in npm help scripts for more information. npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

[INFO] Linting JavaScript… [INFO] Linting HTML…

Config loaded: C:\Program Files\shaka-player.htmlhintrc

Config loaded: C:\Program Files\shaka-player.htmlhintrc

Config loaded: C:\Program Files\shaka-player.htmlhintrc

Scanned 3 files, no errors found (22 ms). [INFO] Checking that the build files are complete… [INFO] Checking the tests for type errors… [INFO] Building the docs… [INFO] Compiling the library (ui, debug)… [INFO] Compiling the library (compiled, debug)… [INFO] Compiling the demo app (debug)… C:/Program Files/shaka-player/demo/cast_receiver/receiver_app.js:19: ERROR - required “goog.asserts” namespace never provided goog.require(‘goog.asserts’); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

1 error(s), 0 warning(s) [ERROR] Build failed

What did you expect to happen? Build Shaka and have npm bring in all the dependencies in the package.json

What actually happened? Got an npm package required error. I tried fixing this with npm audit fix without sucess.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
joeyparrishcommented, Jan 8, 2019

This seems to be a bug in our build scripts regarding how path names are handled. It should be fairly easy to fix.

0reactions
joeyparrishcommented, Jan 22, 2019

Fix cherry-picked for v2.4.6.

Read more comments on GitHub >

github_iconTop Results From Across the Web

`namespace never provided` Error with closure-compiler.jar
Problem statement I follow Advanced Compilation tutorial to try. I did not create a new directory in the Blockly root directory to test, ......
Read more >
Google Blockly `namespace never provided` Error with ...
Usually the 'Namespace never provided' error is caused by not passing the file that provides that namespace to the compiler.
Read more >
Resolving compile dependencies on the Closure Library
1> Content\Scripts\closure\goog\net\xpc\nativemessagingtransport.js:26: ERROR - required "goog.async.Deferred" namespace never provided.
Read more >
google_input_tools/third_party/closure_library/closure/goog ...
In uncompiled mode base.js will write out Closure's deps file, unless the ... elsewhere) the namespace may never be required and thus, not...
Read more >
closure-library/closure/goog/base.js - Physics Simulations
302, // A goog.module/goog.provide maps a goog.require to a specific file. 303, if (goog.isProvided_(name)) {. 304, throw new Error('Namespace "' + name + ......
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