Hi, @chiedo . What do you think about supporting latest react version? Also halogen library with loaders freezed and doesn't support it. I can do PR if you don't mind

Hi, The CORS limitation can be avoided, this is mostly depending on the server's CORS configuration which might allow all origins to access the file.

On the client side, the THREE.js loaders actually support this, but needs to have an attribute set: In STLViewer.js, right after: let loader = new THREE.STLLoader();, Setting loader.crossOrigin = '';, allows loading external STL files.

I'm not if this should be set using an optional parameter or is this OK as a default, but anyway it works and removes the same origin limitation, as long as the server is configured correctly.

Would love to hear your thoughts on this. Thanks!

I added the ability to read the binary colors of the file. now, if the file has colors, it will be seen. example for a colored file, from three.js official site: https://threejs.org/examples/models/stl/binary/colored.stl.

note: in that case, when there is binary colors, the modelColor parameter does not needed and will not affect.

Currently, if you update any property, the STLViewer component will create an instance of the Paint class. Then the Paint class will create an instance of Scene, WebGLRenderer, etc. But it's not necessary to create them again. I'm not sure this will cause a memory leak or not but, creating a new Mesh and not removing the last one, definitely will(especially after updating the url property). Another case is when STLViewer component unmounts. We should deallocate the mesh, scene and WebGL renderer. I'm using this module on a project and by changing the STL file URL over and over, I got 1.5GB usage of GPU memory. After this fix, it only uses the memory it needs(with the same files the maximum usage was 132MB).

Hi I have refactored the code to avoid to duplicate logic, also I tried to add an style in the files, It would be amazing if we implemented some style guide like airbnb in next iterations 😄

I've found an unpleasant behavior on loading file. Wrapper element much higher on loading and when it is loaded wrapper jumps to specified height.

Also I get dig into your code and found the solution.

Hey, This fixes an issue when some files are rendered "all black" even when the color is set. This happens because of missing normals data that the shader relies on.

Hey guys, i made this little things that permits to load also a file directly and not only from an url. The PR create a breaking change:

• url prop is removed
• model prop is added. This can be a string (maintain the old behaviour) or an ArrayBuffer.

I add a button in the example to recreate the upload behavior.

NOTE: the Three.js file is all changed due to the autoformatter of my editor that change the tabs with the spaces. Now the file is aligned with the rest of the project.

When the model rotates freely, light source is static and we can see the model in the light from all sides. When user rotates the model manually by mouse drag, the lights rotate too - the sides of the model stay either in the light or in the shadow (and therefore the sides in the shadow are impossible to see).

My current rendered object has a lot of shadows that is hiding some geometric details. Is there any way to turn off the shadow effect?? or perhaps reduce it to a minimum??

Currently, installing the package raises the following error: npm ERR! peer dep missing: [email protected]^4.3.2, required by [email protected]

This is because in version 2.3.0 of halogenium, a peer dependency ([email protected]^4.3.2) was added to it.

This PR specifies a more specific required version of halogenium to avoid this issue.

I'm having issues with a new project. I'm getting the following:

Failed to compile.

./node_modules/halogenium/lib/BeatLoader.js
Module not found: Can't resolve 'styled-components' in '/Users/user/Development/render-test/react/node_modules/halogenium/lib'

Any suggestions?