Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cesium version issue #11281

Closed
pyp123 opened this issue May 15, 2023 · 1 comment
Closed

Cesium version issue #11281

pyp123 opened this issue May 15, 2023 · 1 comment

Comments

@pyp123
Copy link

pyp123 commented May 15, 2023

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?

@ggetz
Copy link
Contributor

ggetz commented May 16, 2023

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.

Thanks!

@ggetz ggetz closed this as completed May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants