# How to build newest cesium(cesium1.114)

**URL:** <https://community.cesium.com/t/how-to-build-newest-cesium-cesium1-114/30019>\
**Category:** CesiumJS\
**Created:** [February 20, 2024, 8:48am UTC](https://community.cesium.com/t/how-to-build-newest-cesium-cesium1-114/30019 "2024-02-20T08:48:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![qq7700kk](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/qq7700kk/32/14037_2.png) [@qq7700kk](https://community.cesium.com/u/qq7700kk)\
**Post date:** [February 20, 2024, 8:48am UTC](https://community.cesium.com/t/how-to-build-newest-cesium-cesium1-114/30019/1 "2024-02-20T08:48:20Z")

</div>

download cesium1.114,when i use commond “npm run build”,it show me "npm ERR! Missing script: ‘build’  
",so i open package.json,there is no build in scrips,i modify some code there,I would like to ask how to build it

---

<div class="post-metadata">

**Author:** ![jjspace](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/jjspace/32/4102_2.png) [@jjspace](https://community.cesium.com/u/jjspace)\
**Post date:** [February 20, 2024, 2:32pm UTC](https://community.cesium.com/t/how-to-build-newest-cesium-cesium1-114/30019/2 "2024-02-20T14:32:22Z")

</div>

If you’re looking to contribute to CesiumJS directly you can follow our [contributing guide](https://github.com/CesiumGS/cesium/blob/main/CONTRIBUTING.md). If you’re looking to use Cesium in your own application you should not have to build it directly and can use the non package directly

---

<div class="post-metadata">

**Author:** ![s3xysteak](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/s3xysteak/32/19939_2.png) [@s3xysteak](https://community.cesium.com/u/s3xysteak)\
**Post date:** [February 25, 2024, 8:56am UTC](https://community.cesium.com/t/how-to-build-newest-cesium-cesium1-114/30019/3 "2024-02-25T08:56:19Z")

</div>

It seems that you want to build a project with Cesium instead of building CesiumJS directly. If you are using Vite, try [vite-plugin-cesuium-build](https://github.com/s3xysteak/vite-plugin-cesium-build). Or see the CesiumJS official tutorial about building with webpack.  
If you are creating a library about CesiumJS, just make cesium external.

---

<div class="post-metadata">

**Author:** ![qq7700kk](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/qq7700kk/32/14037_2.png) [@qq7700kk](https://community.cesium.com/u/qq7700kk)\
**Post date:** [April 28, 2024, 2:33am UTC](https://community.cesium.com/t/how-to-build-newest-cesium-cesium1-114/30019/4 "2024-04-28T02:33:53Z")

</div>

thank you very much

---

<div class="post-metadata">

**Author:** ![fa\_yang](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/fa_yang/32/23223_2.png) [@fa\_yang](https://community.cesium.com/u/fa_yang)\
**Post date:** [April 29, 2024, 11:27pm UTC](https://community.cesium.com/t/how-to-build-newest-cesium-cesium1-114/30019/5 "2024-04-29T23:27:55Z")

</div>

Could you please help me look into this issue?

> [@Webworker cross origin vite viteStaticCopy](https://community.cesium.com/t/webworker-cross-origin-vite-vitestaticcopy/31747):
>
> use vite project, viteStaticCopy to copy cesium statics when cross origin, other assets is ok, but the webwork goes wrong. 1.what i a encounter(Problem Description) I am developing an SDK based on Cesium within a Vite project. After using viteStaticCopy to copy all of Cesium’s static files, I encounter a problem when accessing these files from another Vite project (running on a different localhost port). While images do not trigger any cross-origin issues, web workers do face these problems. H…