@rayu-dev/rayu-cli 2.0.11 → 2.0.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/rayu.js +3314 -4257
- package/package.json +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@rayu-dev/rayu-cli",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.12",
|
|
4
4
|
"description": "Rayu-CLI — a multi-provider AI coding CLI",
|
|
5
5
|
"//": "There are deliberately NO runtime `dependencies`. scripts/build.ts bundles every import into the single published file dist/rayu.js, so nothing has to be resolvable from node_modules at runtime — the only unbundled specifiers are the optional native/OTEL modules in that script's EXTERNAL list, each guarded by a try/catch. Declaring them as dependencies anyway made `npm install -g` resolve, download and compile ~80 packages (including sharp's platform prebuilds) that the CLI never loads, which is what made a global install fail differently on every machine. Add build-time packages to devDependencies. If you ever add a module that must be require()d from node_modules at runtime, it belongs in dependencies AND in the installer's expectations (rayu-web/public/install.sh extracts only dist/rayu.js).",
|
|
6
6
|
"type": "module",
|