New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

functionalscript

Package Overview
Dependencies
Maintainers
0
Versions
452
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

functionalscript - npm Package Compare versions

Comparing version 0.0.586 to 0.0.587

issues/esm.md

23

issues/README.md
# Issues
## Allow Debugging During Test Run
- [test-debug](./test-debug.md).
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`

@@ -18,16 +12,11 @@

`version` property should be
- `version` calculated on a `main` branch.
`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
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`?
{
"name": "@functionalscript/functionalscript",
"version": "0.0.586",
"version": "0.0.587",
"exports": "./index.f.cjs"
}
{
"name": "functionalscript",
"version": "0.0.586",
"version": "0.0.587",
"description": "FunctionalScript is a functional subset of JavaScript",

@@ -5,0 +5,0 @@ "main": "index.f.cjs",

@@ -34,2 +34,3 @@ # FunctionalScript

FunctionalScript code can be used:
- in any JavaScript/TypeScript application,

@@ -36,0 +37,0 @@ - as a JSON with expressions,

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc