Dave Herman
Dave Herman
**Your Environment** * **verdaccio version**: 5.26.3 * **node version** [12.x.x, 14.x.x]: v18.18.0 * **package manager**: npm@9 * **os**: linux * **platform**: GitHub Actions (Docker) **Describe the bug** When run in...
I'm thinking maybe we shouldn't lazily read the config file, since it means we can get late errors after Volta does some work. It's probably best to just fail out...
Backtraces would be useful for verbose diagnostics, not just for Volta maintainers. But we don't want to require Volta users to know about the `RUST_BACKTRACE` environment variable (and it could...
Add to `create-neon` the ability to create Neon libraries with sensible zero-config defaults set up for pre-builds, including fully functional CI/CD. ``` % npm init neon -y --lib example-project Wrote...
Implements #966. Implementation notes: - Core functionality implemented in `crates/cargo-cp-artifact` as a regular crate - `crates/cargo-cp-artifact` also has a bin so it can be used to build the self-hosted JS...
As a dogfood opportunity, port the `cargo-cp-artifact` tool to Rust using Neon. This will also serve as a useful test vehicle for creating prebuild functionality.
It would be nice to have convenience types for common globals like `console`, `process`, and `JSON`. We could imagine it might look something like: ```rust struct Console Console
Currently the prolyfill uses this code for testing whether a value is a Future: ``` javascript !!x && typeof x.then === 'function' && x.then.length === 2 ``` The issue with...
Compilation strategy: - parse with Esprima - pre-define all vars on global object as undefined - pre-define all functions on global object via Function constructor - construct one evalable string...