You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why did the previous cesium project architecture default to a build folder, but newer versions do not have this folder? Also, after using the 'npm run start' command to run cesium in the past, clicking on the 'sandcastle' link to see various model instances without displaying any background information? But the latest one can be displayed. From which version did the cesium project architecture undergo major changes?
The text was updated successfully, but these errors were encountered:
CesiumJS is a big project, so we use GitHub for feature requests and bug tracking exclusively. In the future, please take any questions to the Cesium Forum where there are members of the community and developers from the team who can help.
We'll likely need some more context to answer. Build artifacts still get output to a Build directory. There was a change in the project archectecture to support npm workspaces in #10824, but there have been other changes as well.
Also nothing major has changed with Sandcastle recently. If you explain the issue in more detail we may be able to track down what it is.
Why did the previous cesium project architecture default to a build folder, but newer versions do not have this folder? Also, after using the 'npm run start' command to run cesium in the past, clicking on the 'sandcastle' link to see various model instances without displaying any background information? But the latest one can be displayed. From which version did the cesium project architecture undergo major changes?
The text was updated successfully, but these errors were encountered: