Skip to main content
SimilarExport ZIP
100%

Demo PKG binary to serve html content

✓ Published0🌍 Public
TThomasG77
Last edited Sep 30, 2021
Created on Sep 30, 2021

This example demonstrates how to package a static website into a standalone executable binary using the `pkg` tool. The code uses Express to serve the contents of a `dist` folder, which it retrieves by downloading and unzipping the `doc.data.gouv.fr` GitHub Pages repository via a shell script. After building the binary with `npm run build`, the user can launch it on any OS and access the site at `http://localhost:8081/`. The visualization highlights the workflow of converting web content into a portable, offline server application.

AI-generated description

Demo PKG binary to serve html content

Steps to test

  • Execute ./retrieve.sh
  • Install pkg with npm i -g pkg
  • npm run build to build binary
  • click on the binary if through GUI otherwise , via a command line, do either ./server-static-offline-linux, ./server-static-offline-macos or server-static-offline-win.exe depending of your OS.
  • open a browser at http://localhost:8081/ to see local website
ISC Licensed

Similar vizzes

Loading thumbnail…

bundle/index.html for webpack-es6-boilerplate

This example shows a minimal webpack setup for an ES6 project, producing a single-page HTML document that loads a compiled JavaScript bundle. The page contains no visible content or user interface, only an empty body with a script tag referencing `bundle.js`. The code demonstrates the entry-point plumbing of a webpack-built application, where the frontend relies entirely on the bundled output for any rendering or behavior. The files include the `index.html` shell and the webpack configuration source, indicating how a boilerplate project connects its build system to a basic HTML host page.

115Dkatz
54% match
Loading thumbnail…

Gist 7ea7490cb95fe21dfad10572a1c8244f

This example visualizes the process of checking and updating the UPX executable packer to its latest release version. It shows a shell-script-driven workflow that queries the GitHub API for the newest release tag, compares it to the locally installed version, and either reports the tool is up to date or proceeds to download, compile, and install the source tarball. The code relies on standard command-line utilities (`curl`, `jq`, `tar`, `make`) and directly parses version strings, without any graphical or interactive rendering libraries. The rendering approach is purely textual terminal output, with no data visualization beyond status messages.

HHerst
52% match
Loading thumbnail…

Gist 0bdc45cce93d15fce0d1991d2b4b9e9d

This example demonstrates how to convert a compressed LiDAR point-cloud dataset from IGN’s French national archive into a ZIP archive for easier distribution. The shell script downloads a 7z file via `wget`, decompresses it with `unp`, recompresses the contents into a ZIP using `zip`, and then reports the final disk usage with `du -cksh`. It relies on standard command-line utilities rather than JavaScript libraries, showing a practical data-preparation workflow for large geospatial files.

TThomasG77
51% match
Loading thumbnail…

Gist 75fe6f98cacb874f8d9ebce7248b1b66

This example presents a web-based client-server application that serves static files and handles socket connections. The server is built with Express and Socket.IO, listening on a configurable port, and delegates all routes to a single `index.html` file. It uses the `body-parser` middleware for JSON parsing and the `path` module to resolve file locations. The rendering approach is not specified, but the code clearly establishes the infrastructure for delivering a front-end visualization, with the server acting as the backbone for real-time communication and static asset delivery.

RRonolibert
51% match
Loading thumbnail…

Fork of HTML Starter

This example displays a single static message, “Hello KPR!”, styled with large red text on a blue background. It uses standard HTML and CSS to define the layout and appearance, while a JavaScript file, loaded as a module, runs a simple `console.log` command. The visualization demonstrates a minimal setup for combining an HTML document with external CSS and JavaScript files, serving as a basic template for more complex projects.

PPremkumar
51% match
Loading thumbnail…

Fork of HTML Starter

This example renders a static webpage that displays the text “Hello HTML!” prominently in the browser. The page is built with a simple HTML structure that links to a separate stylesheet, which uses CSS to style the message with a large font size. The JavaScript file contains only a console log statement, showing no interactive or data-driven visualization features. The example relies on standard web technologies—HTML, CSS, and JavaScript—rather than any specific data-processing or charting libraries.

Wwjo672@haw-hamburg.de
50% match
Loading thumbnail…

requirebin sketch

This example demonstrates a minimal client-side application that loads a data package from a remote URL using the `chi-datapackage` library, then manages the resulting state through the `barracks` event-based architecture. The code shows a unidirectional data flow where a `loadPackage` effect triggers a `replacePackage` reducer to update the application state. It also logs actions and state changes for debugging. The visualization itself is not rendered in the provided files; instead, the focus is on the data-loading and state-management pipeline, with the package.json specifying the required dependencies for this workflow.

HHypercubed
50% match
Loading thumbnail…

Demo

This minimal example presents a blank HTML page with the title "Demo." It contains no data visualization, charts, or interactive elements. The code consists solely of a basic HTML document structure, including a head section with a title tag and an empty body element. It does not utilize any external libraries, APIs, or data sources, and therefore renders no graphical or data-driven output. The page simply displays the browser's default view with no content.

Aabhaykumarsinha-aks
50% match