functionalscript 0.0.583 → 0.0.585
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/issues/README.md +9 -2
- package/jsr.json +1 -1
- package/package.json +1 -1
package/issues/README.md
CHANGED
|
@@ -6,7 +6,7 @@ Currently, we read files as strings and then parse them as functions. See [dev/t
|
|
|
6
6
|
|
|
7
7
|
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`.
|
|
8
8
|
|
|
9
|
-
**Note:**
|
|
9
|
+
**Note:** In this case, we will drop support for Deno v1.
|
|
10
10
|
|
|
11
11
|
## Creating `./index.f.cjs`
|
|
12
12
|
|
|
@@ -18,6 +18,13 @@ Currently, we regenerate [./index.f.cjs](./index.f.cjs) using `npm run index` du
|
|
|
18
18
|
`version` property should be
|
|
19
19
|
- `version` calculated on a `main` branch.
|
|
20
20
|
|
|
21
|
+
## Publishing
|
|
22
|
+
|
|
23
|
+
Before publishing, we have to be sure that
|
|
24
|
+
1. [index.f.cjs](./index.f.cjs) is up to date
|
|
25
|
+
2. `version` is updated in [jsr.json](./jsr.json) and [package.json](./package.json).
|
|
26
|
+
|
|
21
27
|
## Switching to ESM
|
|
22
28
|
|
|
23
|
-
Currently, the biggest obstacle
|
|
29
|
+
Currently, the biggest obstacle to using ESM is that we cannot make bundles on ESM modules without an FS parser.
|
|
30
|
+
The solution is to deploy ESM modules to HTTPS.
|
package/jsr.json
CHANGED