sendscript 0.1.2 → 0.1.4

package/CHANGELOG.md

@@ -4,8 +4,21 @@ All notable changes to this project will be documented in this file. Dates are d
 
 Generated by [`auto-changelog`](https://github.com/CookPete/auto-changelog).
 
+#### [v0.1.4](https://github.com/bas080/sendscript/compare/v0.1.3...v0.1.4)
+
+- Add missing index file that exports both modules [`38054ea`](https://github.com/bas080/sendscript/commit/38054ea8284a1626146bec42309b3c014527ff7d)
+- Prevent ref of non existant property on env object [`49520ad`](https://github.com/bas080/sendscript/commit/49520ad32604683c668d95e479de772a91f6ae2b)
+
+#### [v0.1.3](https://github.com/bas080/sendscript/compare/v0.1.2...v0.1.3)
+
+> 21 January 2024
+
+- Remove the d.ts file gen step [`801b2cf`](https://github.com/bas080/sendscript/commit/801b2cf3b38259455186d4df85d98a42c046287c)
+
 #### [v0.1.2](https://github.com/bas080/sendscript/compare/v0.1.1...v0.1.2)
 
+> 4 January 2024
+
 - Update tap to 10.9.5 [`4e3ddcc`](https://github.com/bas080/sendscript/commit/4e3ddcca823ca64c52bc1966ac23a712480d6c4d)
 
 #### [v0.1.1](https://github.com/bas080/sendscript/compare/v0.1.0...v0.1.1)

package/README.md

@@ -193,21 +193,18 @@ There is a good use-case to write an environment module in TypeScript.
    coding.
 2. You can use tools like [typedoc][typedoc] to generate docs from your types to
    share with consumers of your API.
-3. You can generate a .d.ts with `tsc --declaration` and use it to coerce your
-   client to adopt the modules type.
+3. You can use the types of the module to coerce your client to adopt the
+   modules type.
 
 ```bash
 # Create pretty docs for your module.
 npx typedoc my-module.ts
-
-# Create the .d.ts file for your module.
-tsc --declaration
 ```
 
-Now we can use the `my-module.d.ts` file for the client API.
+Now we can use the `my-module.ts` file for the client API.
 
 ```ts
-import type * as MyModule from './my-module.d.ts'
+import type * as MyModule from './my-module'
 
 import sendScriptApi from 'sendscript/api.mjs'
 
@@ -233,19 +230,19 @@ npm t -- report text-summary
 ```
 ```
 
-> sendscript@0.1.2 test
+> sendscript@0.1.4 test
 > tap -R silent
 
 
-> sendscript@0.1.2 test
+> sendscript@0.1.4 test
 > tap report text-summary
 
 
 =============================== Coverage summary ===============================
-Statements   : 100% ( 98/98 )
-Branches     : 100% ( 30/30 )
+Statements   : 100% ( 110/110 )
+Branches     : 100% ( 32/32 )
 Functions    : 100% ( 10/10 )
-Lines        : 100% ( 98/98 )
+Lines        : 100% ( 110/110 )
 ================================================================================
 ```
 

package/README.mz

@@ -174,21 +174,18 @@ There is a good use-case to write an environment module in TypeScript.
    coding.
 2. You can use tools like [typedoc][typedoc] to generate docs from your types to
    share with consumers of your API.
-3. You can generate a .d.ts with `tsc --declaration` and use it to coerce your
-   client to adopt the modules type.
+3. You can use the types of the module to coerce your client to adopt the
+   modules type.
 
 ```bash
 # Create pretty docs for your module.
 npx typedoc my-module.ts
-
-# Create the .d.ts file for your module.
-tsc --declaration
 ```
 
-Now we can use the `my-module.d.ts` file for the client API.
+Now we can use the `my-module.ts` file for the client API.
 
 ```ts
-import type * as MyModule from './my-module.d.ts'
+import type * as MyModule from './my-module'
 
 import sendScriptApi from 'sendscript/api.mjs'
 

package/exec.mjs

@@ -3,6 +3,9 @@ import curry from './curry.mjs'
 
 const debug = _debug.extend('lisp')
 
+class SendScriptError extends Error {};
+class RefError extends SendScriptError {};
+
 const exec = curry(async (env, expression) => {
   debug('exec', expression)
 
@@ -22,10 +25,19 @@ const exec = curry(async (env, expression) => {
   if (operator === 'ref') {
     const [name] = args
 
+    if (!Object.hasOwn(env, name)) {
+      throw new RefError(expression)
+    }
+
     return env[name]
   }
 
   return await Promise.all(expression.map(exec(env)))
 })
 
+export {
+  SendScriptError,
+  RefError
+}
+
 export default exec

package/exec.test.mjs

@@ -38,5 +38,9 @@ test('should evaluate basic expressions correctly', async (t) => {
     [1, 2, 3]
   )
 
+  t.rejects(async () => {
+    await evaluate(['ref', 'doesNotExist'])
+  })
+
   t.end()
 })

package/index.mjs

@@ -0,0 +1,4 @@
+import api from './api.mjs'
+import exec from './exec.mjs'
+
+export default { api, exec }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sendscript",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "description": "Blur the line between server and client code.",
   "module": true,
   "main": "index.mjs",