functionalscript 0.0.586 → 0.0.588

package/.github/workflows/ci.yml

@@ -10,21 +10,7 @@ on:
   pull_request:
 
 jobs:
-  locks:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v2
-    - uses: actions/setup-node@v2
-      with:
-        node-version: 22
-    - run: npm install
-    - uses: actions/upload-artifact@v4
-      with:
-        name: package-lock.json
-        path: package-lock.json
-
   node:
-    needs: locks
     runs-on: ubuntu-latest
 
     strategy:
@@ -37,9 +23,6 @@ jobs:
     - uses: actions/setup-node@v2
       with:
         node-version: ${{ matrix.node-version }}
-    - uses: actions/download-artifact@v4
-      with:
-        name: package-lock.json
     - run: npm ci
     - run: npm test
     - run: npm run version
@@ -70,7 +53,6 @@ jobs:
     - run: /home/runner/.bun/bin/bun ./dev/test.mjs
 
   COM:
-    needs: locks
     strategy:
       matrix:
         os: ['ubuntu-latest', 'windows-latest', 'macos-14']
@@ -82,9 +64,6 @@ jobs:
     - uses: actions/setup-node@v2
       with:
         node-version: 22
-    - uses: actions/download-artifact@v4
-      with:
-        name: package-lock.json
     - uses: actions/setup-dotnet@v3
       with:
         dotnet-version: 9

package/Cargo.lock

@@ -0,0 +1,14 @@
+# This file is automatically @generated by Cargo.
+# It is not intended for manual editing.
+version = 3
+
+[[package]]
+name = "nanocom"
+version = "0.2.1"
+
+[[package]]
+name = "testrust"
+version = "0.1.0"
+dependencies = [
+ "nanocom",
+]

package/README.md

@@ -31,6 +31,7 @@ In FunctionalScript:
 ## Applications
 
 FunctionalScript code can be used:
+
 - in any JavaScript/TypeScript application,
 - as a JSON with expressions,
 - as a query language.

package/com/rust/nanocom/Cargo.lock

@@ -0,0 +1,7 @@
+# This file is automatically @generated by Cargo.
+# It is not intended for manual editing.
+version = 3
+
+[[package]]
+name = "com"
+version = "0.1.0"

package/issues/README.md

@@ -1,32 +1,5 @@
 # Issues
 
-## Allow Debugging During Test Run
-
-Currently, we read files as strings and then parse them as functions. See [dev/test.mjs](dev/test.mjs). In this case, the debugger doesn't know about the source code and can't debug the functions. The main reason for loading modules as functions was that Deno v1 didn't support `.cjs` files. However, Deno v2 supports them.
-
-We can fix the issue by changing our test runner. The test runner will scan all directories, find all `test.f.cjs` files, and then load them using `require`.
-
-**Note:** In this case, we will drop support for Deno v1.
-
-## Creating `./index.f.cjs`
-
-Currently, we regenerate [./index.f.cjs](./index.f.cjs) using `npm run index` during CD (publishing). However, we don't check in CI if it was regenerated. The idea is that CI should check if all generated files in Git are updated:
-- [package.json](./package.json) `version` property
-- [jsr.json](./jsr.json), `version` property
-- [index.f.cjs](./index.f.cjs)
-
-`version` property should be
-- `version` calculated on a `main` branch.
-
-## Publishing
-
-Before publishing, we have to be sure that 
-1. [index.f.cjs](./index.f.cjs) is up to date
-2. `version` is updated in [jsr.json](./jsr.json) and [package.json](./package.json).
-
-## Switching to ESM
-
-Currently, the biggest obstacle to using ESM is that we cannot make bundles on ESM modules without an FS parser. 
-The solution is to deploy ESM modules to HTTPS.
-
-## Can we get rid of `jsr.json` and use only `package.json`?
+1. [test-debug](./test-debug.md).
+2. [esm](./esm.md)
+3. [publish](publish.md)

package/issues/esm.md

@@ -0,0 +1,8 @@
+# Switching to ESM
+
+We need ESM for such systems like Deno, JSR and browsers.
+
+Currently, the biggest obstacle to using ESM is that we cannot make bundles on ESM modules without an FS parser.
+The solution is to deploy ESM modules to HTTPS.
+
+This task depends on [test-debug](./test-debug.md).

package/issues/publish.md

@@ -0,0 +1,45 @@
+# Publishing Packages
+
+We are targeting the following systems:
+
+- JS:
+  - NPM
+  - JSR
+  - https://esm.sh/ optional
+- Rust:
+  - https://crates.io/
+
+## Creating `./index.f.cjs`
+
+Currently, we regenerate [./index.f.cjs](./index.f.cjs) using `npm run index` during CD (publishing). However, we don't check in CI if it was regenerated. The idea is that CI should check if all generated files in Git are updated:
+
+- [package.json](./package.json) `version` property
+- [jsr.json](./jsr.json), `version` property
+- [index.f.cjs](./index.f.cjs)
+
+`version` property should be `version` calculated on a `main` branch.
+
+We may abandon the idea to publish on every commit on `main`. Instead, we will publish only we when we update a version in the `main` branch. This strategy can also work for Rust packages. The idea is that people can still reference from Git if they would like to have a not-published version of a package. We will still release in CI but only when there is a new version.
+
+## Publishing
+
+Before publishing, we have to be sure that
+
+1. [index.f.cjs](./index.f.cjs) is up to date
+2. `version` is updated in [jsr.json](./jsr.json) and [package.json](./package.json).
+
+## CI Jobs
+
+### 1. Publishing (merge to `main`)
+
+Check if the version is new, then publish.
+
+### 2. CI
+
+Errors:
+
+- correct `index.f.mjs` is merged.
+
+Warnings (not blocking CI):
+
+- out of date lock files, such as `package-lock.json` and `Cargo.lock`.

package/issues/test-debug.md

@@ -0,0 +1,12 @@
+# Allow Debugging During Test Run
+
+Currently, we read files as strings and then parse them as functions. See [dev/test.mjs](../dev/test.mjs). In this case, the
+debugger doesn't know about the source code and can't debug the functions. The main reason for loading modules as functions was
+that Deno v1 didn't support `.cjs` files. However, Deno v2 supports them.
+
+We can fix the issue by changing our test runner. The test runner will scan all directories, find all `test.f.cjs` files, and
+then load them using `require`.
+
+Limitations: we will not able to check test module dependencies to have module coverage but, anyway, without a parser, we are not able to get full coverage. So, we can drop support for it right now.
+
+**Note:** In this case, we may drop support for Deno v1. At least until we switch to [ESM](./esm.md).

package/jsr.json

@@ -1,5 +1,5 @@
 {
   "name": "@functionalscript/functionalscript",
-  "version": "0.0.586",
+  "version": "0.0.588",
   "exports": "./index.f.cjs"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "functionalscript",
-  "version": "0.0.586",
+  "version": "0.0.588",
   "description": "FunctionalScript is a functional subset of JavaScript",
   "main": "index.f.cjs",
   "scripts": {
@@ -31,7 +31,7 @@
   },
   "homepage": "https://github.com/functionalscript/functionalscript#readme",
   "devDependencies": {
-    "@types/node": "^22.10.0",
+    "@types/node": "^22.10.1",
     "typescript": "^5.7.2"
   }
 }