Cotton Hou

Bump depend purescript-installer to ^0.3.1

1

**Description of the change** This bump is to address outdated NPM packages of the installer, see original issue at purescript/npm-installer#32 and its fixing PR purescript/npm-installer#33 --- **Checklist:** - [x] Added...

esnext to es2018

1

Given both **TypeScript** and **ClosureCompiler** have fixed `es2018` targeting, good to lock down `es2018` instead of `esnext`?

Fix the checking lack for event class type

2

By running the new test case against the code of `v0.8`, will be pass through without any fail or error, but throw up an uncatchable `ArgumentError` additionally.

I've seen both GPL and MPL note in the License file, isn't those two are incompatible? Isn't this distribution going to be considered as GPL violation?

options.space in false should at least keep one for safety

9

Consider this edge case: ```javascript var/* jsdoc */age = 42; ``` Which emits: ```javascript varage = 42; ```

This tweak will letting the vite[^1] to leverage the ES2015 export condition in case of rxjs[^2]. [^1]: https://vitejs.dev/config/shared-options#resolve-conditions [^2]: https://rxjs.dev/guide/installation#es2015-via-npm

Improve type inference with `NoInfer` type (`check`, `forward`, ...)

3

For example: ```ts // Number.isSafeInteger(number: unknown): boolean const safeInteger = v.pipe( v.number(), check2(Number.isSafeInteger), // Type 'unknown' is not assignable to type 'number' v.check(Number.isSafeInteger), ); declare function check2( requirement: (input: NoInfer)...

Also publish to JSR?

7

From the **Hono** document: > If you want to use Third-party Middleware with the TypeScript Type inferences, you need to use the npm: specifier. [^deno] For package like `npm:@hono/valibot-validator`, this...

SVG optimization from <rect> to <path>?

2

The current SVG implementation generates multiple `` elements to render the bit blocks. I think it could be optimized by using a single `` within the `` element. This way...