Can't resolve 'goog/asserts.js'
See original GitHub issuewhen I
import OLCesium from 'ol-cesium';
but i got this
./node_modules/ol-cesium/src/olcs/OLCesium.js
Module not found: Can't resolve 'goog/asserts.js' in 'D:\sourcecode\catalog2.0-react\node_modules\ol-cesium\src\olcs'
version: 2.2.2 win10 node: 8.4
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Resolving compile dependencies on the Closure Library
I've been playing around with AngularJS + the Closure Compiler, and now I'm trying to take advantage of the Closure Library, too.
Read more >JSDoc: Source: lib/routing/walker.js - Shaka Player Demo
When the walker is; * ready to change destinations, it will resolve the request, ... If the current route cannot be interrupted, we...
Read more >firebase - UNPKG
node_modules/core-js/internals/promise-resolve.js","../. ... _bodyArrayBuffer = bufferClone(body.buffer)\n // IE 10-11 can't handle a DataView body.\n this.
Read more >Untitled
node_modules/google-closure-library/closure/goog/asserts/asserts.js",". ... of legacy clients, the DOM loader can't be easily removed from\n// base.js.
Read more >shadow-cljs 2019-04-07 | Slack Archive
how big is the .shadow-cljs/babel-worker/babel-worker.js file? ... since the JS world can't decide how to do ESM->CommonJS interop properly.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hopefully I will be able to release a new version next week.
Yes, thank you for your hard work! I’m not sure if it’s related, but I’m getting an assert error using the old-fashioned technique in the latest release. I setup the example locally, worked fine. Then plugged the same ol-cesium into my app and got the following error when new olcs.OLCesium({map:ol2d}) :
TypeError: invalid 'instanceof' operand type assertInstanceof asserts.js:6 createSingleLayerCounterparts VectorSynchronizer.js:106:4 _loop AbstractSynchronizer.js:127:24 addLayers_ AbstractSynchronizer.js:100:28 synchronize AbstractSynchronizer.js:77:4
On client console. Somehow other things (other OL layers, etc) in my real-world app have interfered with the asserts. Let’s see how this 636 fix works out. Thank you!