cesium-webpack-example
February 6, 2024 ยท View on GitHub
A minimal recommended setup for an applications using Cesium with Webpack 4.
Running this application
npm install
npm start
# for the built version
npm run build
npm run start:built
Navigate to localhost:8080.
Available scripts
npm start- Runs a webpack build withwebpack.config.jsand starts a development server atlocalhost:8080npm run build- Runs a webpack build withwebpack.config.jsnpm run start:built- Start a small static server usinghttp-serverto demonstrate hosting the built version
Requiring Cesium in your application
We recommend importing named exports from the Cesium ES module, via the import keyword. This allows webpack to tree shake your application automatically.
Import named modules from Cesium
import { Color } from "cesium";
var c = Color.fromRandom();
Import Cesium static asset files
import "cesium/Build/Cesium/Widgets/widgets.css";
Cesium sub-packages
CesiumJS requires a few static files to be hosted on your server, like web workers and SVG icons. This example is set up to copy these directories already if you install the whole cesium package.
new CopyWebpackPlugin({
patterns: [
{ from: path.join(cesiumSource, "Workers"), to: `${cesiumBaseUrl}/Workers`, },
{ from: path.join(cesiumSource, "ThirdParty"), to: `${cesiumBaseUrl}/ThirdParty`, },
{ from: path.join(cesiumSource, "Assets"), to: `${cesiumBaseUrl}/Assets`, },
{ from: path.join(cesiumSource, "Widgets"), to: `${cesiumBaseUrl}/Widgets`, },
],
}),
However if you only install @cesium/engine then you should change the paths in webpack.config.js to the ones below:
new CopyWebpackPlugin({
patterns: [
{ from: 'node_modules/@cesium/engine/Build/Workers', to: `${cesiumBaseUrl}/Workers` },
{ from: 'node_modules/@cesium/engine/Build/ThirdParty', to: `${cesiumBaseUrl}/ThirdParty` },
{ from: 'node_modules/@cesium/engine/Source/Assets', to: `${cesiumBaseUrl}/Assets` },
],
}),
Additionally you will have to import a different widgets css file in src/index.js.
// Change this import
import "cesium/Build/Cesium/Widgets/widgets.css";
// To this one from the cesium/engine package
import "@cesium/engine/Source/Widget/CesiumWidget.css";
Removing pragmas
To remove pragmas such as a traditional Cesium release build, use the strip-pragma-loader.
Install the plugin with npm,
npm install strip-pragma-loader --save-dev
and include the loader in module.rules with debug set to false.
rules: [
{
test: /\.js$/,
enforce: "pre",
include: path.resolve(__dirname, cesiumSource),
use: [
{
loader: "strip-pragma-loader",
options: {
pragmas: {
debug: false,
},
},
},
],
},
];
Contributions
Pull requests are appreciated. Please use the same Contributor License Agreement (CLA) used for Cesium.
Developed by the Cesium team.