Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
3
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1060319
Regression
Yes
Non-Unity JavaScript files inside the StreamingAssets folder are being compiled as UnityScript files
Steps to reproduce:
1. Open the user-attached project
2. Navigate to Assets/StreamingAssets/html/javascript
3. Open any of the .js files and edit something, add an additional space for example
4. Save and return to Unity
Expected result: the files are not being treated as a part of the project's code
Actual result: the files are being treated as regular Unity scripts, thus causing various compilation errors
Reproduced with: 2018.2.0a1, 2018.2.0f2, 2018.3.0a6
Not reproduced with: 2017.1.3p4, 2017.4.6f1, 2018.1.7f1
Comments (3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
RockingGameDeveloper
Feb 28, 2019 05:23
I created codes in Javascript using Microsoft's Visual Studio Code, yet I can't get them to work in version 2018.3.5f. Any way to fix this issue? Please contact me, I really need to get my game finished and off the ground ASAP. NO, C# and any other code language is not an option, JS or nothing at this point. I am not going to Re-code and entire seven year project.
Kibsgaard
Oct 29, 2018 10:58
Will this fix get added to 2018.2 also?
Work arrounds:
Restart Unity every time you make a change.
or
Downgrade to 2018.1
DDenry
Jul 24, 2018 04:12
Hope 2 resolve this soon. Thank all developers~