Failed to parse source map from... #283
-
Hi, I'm trying to get started with the library but I'm having trouble. I'm running npm install [email protected] in my create-react-app project, but I'm getting an error when trying to import from the Unity library.
I've tried this on both a linux and windows machine. There is no /source directory within my react-unity-webgl folder |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 9 replies
-
I am having this same issue. I have tried the sample files as well as my own build and get this exact same problem. All I am shown when I see the react build is a blank white page. I tried to rollback my unity from 2020 as well as the module and no difference. One thing I personally notice is the files created by unity after build on minimal and default are data.unityweb, js.unityweb, and wasm.unityweb instead of whats stated in examples. Not sure what the issue is here but even with some tweaking I could not find a fix! |
Beta Was this translation helpful? Give feedback.
-
Which version of the module are you using, and what version and language of create react app? |
Beta Was this translation helpful? Give feedback.
-
I believe I have figured out the problem and I can't believe how slow I am for this mistake. My build folder was in my src and not in public. It was as simple as that. I'm guessing the module was looking to grab the files from public folder but couldn't find them which triggered the warning. Sometimes I question my knowledge in programming for mistakes like this haha. So @JoeySpen I recommend making sure your build folder is in public where your index.html and manifest.json is located. |
Beta Was this translation helpful? Give feedback.
-
i have my build directory in public and still getting the same issue |
Beta Was this translation helpful? Give feedback.
-
I've released version v8.7.2 which should resolve this issue. Could you try this and let this board know if it worked for you? Thanks! |
Beta Was this translation helpful? Give feedback.
I've released version v8.7.2 which should resolve this issue. Could you try this and let this board know if it worked for you? Thanks!