quickbundle 0.0.0-next-800b69a → 0.0.0-next-0db4314

package/README.md

@@ -11,19 +11,21 @@
 Quickbundle allows you to bundle a library in a **quick**, **fast** and **easy** way:
 
 - Fast build and watch mode powered by Rollup[^1] and SWC[^2].
-- Compile mode to create a standalone binary for systems that do not have Node.js installed (relies on [Node.js single executable applications feature](https://nodejs.org/api/single-executable-applications.html)).
+- Compile mode to create standalone binaries for systems that do not have Node.js installed[^3].
 - Zero configuration: define the build artifacts in your `package.json`, and you're all set!
 - Support of `cjs` & `esm` module formats output.
 - Support of several loaders including JavaScript, TypeScript, JSX, JSON, and Images.
 - TypeScript's declaration file (`.d.ts`) bundling.
 - Automatic dependency inclusion:
-  - For the build/watch mode, `peerDependencies` and `dependencies` are not bundled in the final output, `devDependencies` are unless they're not imported.
-  - For the compile mode: all dependencies are included to make the code standalone.
+  - For the build and watch mode, `peerDependencies` and `dependencies` are not bundled in the final output, `devDependencies` are unless they're not imported.
+  - For the compile mode, all dependencies are included to make the code standalone.
 
 [^1]: A [module bundler](https://rollupjs.org/) optimized for better tree-shaking processing and seamless interoperability of CommonJS and ESM formats with minimal code footprint.
 
 [^2]: A [TypeScript / JavaScript transpiler](https://swc.rs/) for quicker code processing including TypeScript transpilation, JavaScript transformation, and, minification.
 
+[^3]: It relies on [Node.js single executable applications feature](https://nodejs.org/api/single-executable-applications.html).
+
 <br>
 
 ## 🚀 Quick Start
@@ -98,15 +100,18 @@ yarn add quickbundle
 
 </details>
 
+> [!WARNING]  
+> Critical content demanding immediate user attention due to potential risks.
+
 <details>
-<summary><strong>For compiling single executable applications</strong></summary>
+<summary><strong>For compiling executables</strong></summary>
 
 ```jsonc
 {
 	"name": "lib", // Package name
 	"source": "./src/index.ts", // Source code entry point. Make sure that it starts with `#!/usr/bin/env node` pragme to make the binary portable for consumers who would like to use it by installing the package instead of using the generated standalone executable.
 	"bin": {
-		"your-binary-name": "./dist/index.cjs", // Binary information used to get the executable name from the key and, from the value, the build file to inject into the generated executable.
+		"your-binary-name": "./dist/index.cjs", // Binary information to get the executable name from the key and, from the value, the bundled file to generate from the source code and inject into the executable. The generated executable will be located in the same folder as the bundled file and, dependending on the current operating system running the `compile` command, the executable will be named either `your-binary-name.exe` on Windows or `your-binary-name` on Linux and macOS.
 	},
 	// "bin": "./dist/index.cjs", // Or, if the binary name follows the package name, you can define a string-based `bin` value.
 	"scripts": {
@@ -116,8 +121,15 @@ yarn add quickbundle
 }
 ```
 
-> [!warning] Limitations
-> TODO
+> [!warning]
+> The `compile` command relies on the [Node.js SEA (Single Executable Applications)](https://nodejs.org/api/single-executable-applications.html). This feature comes with some limitations which Quickbundle attempts to address:
+
+> [!warning]
+>
+> The `compile` command relies on the [Node.js SEA (Single Executable Applications)](https://nodejs.org/api/single-executable-applications.html). This feature comes with some limitations which Quickbundle attempts to address:
+>
+> - The source code must not rely on [external dependencies](https://github.com/nodejs/single-executable/discussions/70) 🛑. To partially address this, Quickbundle bundles all dependencies (whatever their types, as long as they're used) and inline dynamic imports by default ✅.
+> - The bundled code must use the CommonJS module system 🛑. To address this, Quickbundle always outputs CJS modules in compile mode ✅.
 
 </details>
 

package/dist/index.mjs

@@ -15,7 +15,7 @@ import os from 'node:os';
 import { gzipSize } from 'gzip-size';
 
 var name = "quickbundle";
-var version = "0.0.0-next-800b69a";
+var version = "0.0.0-next-0db4314";
 
 const CWD = process.cwd();
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "quickbundle",
-  "version": "0.0.0-next-800b69a",
+  "version": "0.0.0-next-0db4314",
   "description": "The zero-configuration transpiler and bundler for the web",
   "author": {
     "name": "Ayoub Adib",