lwjgl.org - Home of Lightweight Java Game Library
The website for LWJGL is build with React. It is a single-page application with client-side routing. It installs a Service Worker in order to work offline.
- Client-side routing
- Service Worker (works offline)
- Tiny production build (entire codebase + content weights less than 300KB gzipped)
- Code splitting at route & component level
- Scroll restoration
- Route preloading
- Proximity based route preloading (see /download page)
- Build Customizer with smart download queue & client-side ZIP generator
- Custom webpack manifest parsing + code minification
- CSS-in-JS with Stitches
- Client is written in Typescript
There is currently no server-side rendering because of hosting constraints.
Static assets are loaded from LWJGL's CDN (AWS CloudFront).
Build status icons are loaded directly from travis-ci.org and appveyor.com.
Three.js is loaded from jsDelivr.
- The website for LWJGL 2 can be found here. A static copy of the old LWJGL website is now hosted directly from S3
- The blog is powered by Ghost.
- The forum is SMF.
- The wiki for LWJGL 2 was MediaWiki. A static copy of the old LWJGL wiki is now hosted directly from S3.
- To install all required npm packages:
npm i- To build styles:
npm run styles- To start the server in dev mode:
node server
# or
npm startOPTIONAL: Monitor for /server changes & auto-restart with:
npm run watch--sourcemap # Enables inline JS source-maps
--nohmr # Disables Webpack Hot Module ReplacementThe following flags are used for testing production builds locally. NODE_ENV environment variable must be set to "production".
--test # Enables production test mode (e.g. disables HSTS)
--nocache # Disables Pug view caching
--pretty # Pretty prints HTML
--s3proxy # Proxies S3 imagesFlag usage examples:
node server --async --nohmr
npm run watch -- --async --nohmrNODE_ENV="production" # default: development
PORT="8080" # default: 80
HOST="127.0.0.1" # default: 0.0.0.0To deploy LWJGL in production please read the separate guide: DEPLOYMENT.md.
git pull
npm i
npm run releaseYou can run the production build locally:
npm run test-productionThe following debugging tips may come in handy:
- Disable minification by uncommenting
minimize: falsein webpack.config.js - Prevent Terser from dropping
console.logordebuggerby changingterserOptionsin terser-config.json - Pass
--profilingto load React profiling builds - Output
namedmodule & chunk ids in webpack.config.js - Analyze build output with
npx webpack-bundle-analyzer public/js/webpack.manifest.json -h 0.0.0.0(for full breakdown, change toall: truewhen writingwebpack.manifest.jsonin build-production.js)