You know what to do... npm install and npm run dev or npm run build then npm run start - Yarn probably works too...
https://hp-sat-viz.vercel.app <- Live demo
Setup an env var called NEXT_PUBLIC_SITE_URL with your running instance's public URL. For local, I use NEXT_PUBLIC_SITE_URL='http://127.0.0.1:3000'
Then I just point Vercel to this repo to build and run automatically.
They're likely decayed objects; i.e., dots that shouldn't be there that I was too lazy to filter out.
If you want to check out how this works, check out ./Components/CesiumComponent.tsx I tried to document much as possible!
I am using this WASM package https://github.com/wasmerio/sgp4; However, I did edit how the wasm package is fetched. Others should be same.
Cesium requires some files to be copied in a publicly accessible folder. This is achieved with CopyWebPackPlugin... BUT each copy statements requires info: { minimized: true }
It is just cleaner to have Cesium related components as client only components. So in this case, both the Cesium component and the dynamic ssr off wrappers are tagged with 'use client'
I won't go into every method that I've tried but every method I've tried has resulted in browser errors, Next.js errors, and/or Vercel (500 status filesystem) errors. Using the CopyWebPackPlugin, wrapping it in a dynamic component, and then finally importing the Cesium files via import inside a useEffect yielded 100% success.
With all the work above, it is very important to utilize the dynamically called Cesium and not import individual functions like you would normally. Also it is very important to type Cesium specific things with import type { xyz } from 'cesium' not import { xyz } from 'cesium'
Thank you to the U.S. Gov for the TLE data. Thank you https://github.com/wasmerio/sgp4 for sgp4 wasm. and please give this repo a star if it was helpful!