three.js: update import not work

0.132.2 has been published with sadness 🙃🙃

0.132.1 has been published with no private class fields 🙃

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

That sounds very unappealing… Babel slows down the dev iteration process considerably.

Probably the only solution is to define these variables in the constructors instead.

Very disappointed with the bundlers ecosystem 😔

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.

Very disappointed with the bundlers ecosystem 😔

Indeed. When using new language features, checking the browser support isn’t enough anymore. Would be great to have something like caniuse but in context of bundlers/transpilers.

🤦‍♂️

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’;

@0.132.0, before # got removed - plus latest troika and postprocessing. Works perfect again with @0.132.2.

Ok not even those.

We could transpile the whole three.module.js with babel for now, and remove the transpilation in a later stage.

Alternative is not using class properties for now.

What do you think @mrdoob?

People, could you test if the latest version is working fine? Are normal class properties supported at least?