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.
"export 'LineMaterial' was not found in 'three'
See original GitHub issue报错
ERROR in ./node_modules/maptalks.three/dist/maptalks.three.es.js 1986:58-70 "export 'LineMaterial' was not found in 'three' ERROR in ./node_modules/maptalks.three/dist/maptalks.three.es.js 2098:58-70 "export 'LineMaterial' was not found in 'three' ERROR in ./node_modules/maptalks.three/dist/maptalks.three.es.js 5950:4-10 "export 'worker' was not found in 'maptalks' ERROR in ./node_modules/maptalks.three/dist/maptalks.three.es.js 6003:4-10 "export 'worker' was not found in 'maptalks' ERROR in ./node_modules/maptalks.three/dist/maptalks.three.es.js 6008:7-13 "export 'worker' was not found in 'maptalks'
版本使用情况 “three”: “^0.97.0”, “maptalks”: “^0.47.5”, “maptalks.three”: “^0.11.2”,
es6 使用方式 import * as THREE from “three”; import * as maptalks from “maptalks”; import { ThreeLayer } from “maptalks.three”;
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
使用umd 包 from ‘maptalks.three/dist/maptalks.three.js’ 试试,不过我这边 是个警告，其他小伙伴反映也是警告
close by https://github.com/maptalks/maptalks.three/commit/6357ece599cc7748dbda88012b0d9fd4b096340e