To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.
-
name: bun
-
description: Bun is an all-in-one toolkit for JavaScript and TypeScript apps. It ships as a single executable called
bun.At its core is the Bun runtime, a fast JavaScript runtime designed as a drop-in replacement for Node.js. It’s written in Zig and powered by JavaScriptCore under the hood, dramatically reducing startup times and memory usage.
Bun also includes a test runner, script runner, and Node.js-compatible package manager.
-
snapcraft: bun-snap/snap/snapcraft.yaml at main · canonical/bun-snap · GitHub
-
upstream-relation: unrelated
-
supported-category: compilers
-
reasoning: bun itself might work in toy scenarios but this limits applicability in CI/CD environments where $HOME is strongly unrelated to the current working directory (e.g. GitHub Actions). I believe using strict would put too much friction at this stage.
I understand that strict confinement is generally preferred over classic.
I’ve tried the existing interfaces to make the snap to work under strict confinement.
Note that snappy-debug can be used to identify possible required interfaces. See https://snapcraft.io/docs/debug-snaps for more information.