update import not work

[hqzh]

if version is r128，it's working

when i update and just write

import * as THREE from "three";

• Device:Desktop
• OS:Windows7
• Browser:Chrome
• Three.js version: r132
• lang: VUE

[adrianlx]

i have the same issue. please let me know when u solve that.

[marcofugaro]

@hqzh what build system and what version are you using? It looks like create-react-app?

[CodyJasonBennett]

That looks like the general Webpack error overlay but I'm also getting this with CRA.

[LinoPhil]

Same problem here, but only when bundling everything with rollup. I also use # privates in my viewer code and had no problems so far. Maybe rollup needs another option for the three stuff... i have to figure out...

Update:
For me its the terser plugin!

[mrdoob]

Was it too early to start using private class variables? Should we rename #alphaTest to _alphaTest?

[mjurczyk]

what build system and what version are you using? It looks like create-react-app?

@marcofugaro yep, happening in facebook/create-react-app. It's not really an issue with three (support for private fields is quite good) - but create-react-app seems to use an older version on babel.

Adding latest @babel/preset-env does solve the issue, but requires ejecting / taking apart the create-react-app bundle 😔

[hqzh]

what build system and what version are you using? It looks like create-react-app?

@marcofugaro yep, happening in facebook/create-react-app. It's not really an issue with three (support for private fields is quite good) - but create-react-app seems to use an older version on babel.

Adding latest @babel/preset-env does solve the issue, but requires ejecting / taking apart the create-react-app bundle

happening in vue-cli my here

[gkjohnson]

Can confirm this was broken for the /examples/ module imports as well in r132. For example, loading BufferGeometryUtils in an ES6 module from cdn.skypack.dev results in a console warning saying that the BufferGeometryUtils module was not exported.

This is unrelated to the use of private variables. If you look at the release notes you'll see that the exports have changed:

https://github.com/mrdoob/three.js/wiki/Migration-Guide#131--132

BufferGeometryUtils is now imported using this pattern: import * as BufferGeometryUtils from './jsm/utils/BufferGeometryUtils.js';

[marcofugaro]

Yeah current bundlers are not quite ready for private class properties yet.

Newer version of bundler tools such as create-react-app 5.0 alpha are rolling out and they support private properties fine.

[LinoPhil]

For my full viewer bundle I could fix the problem by excluding three from beeing excluded from babel:
//exclude: 'node_modules/**',
exclude: '/node_modules/(?!three)/',

[mrdoob]

0.132.1 has been published with no private class fields 🙃