David Vázquez Púa

#j:require doesn't work on NodeJS

1

I would expect #j:require to evaluate to the require function, but it doesn't happen. Instead, it returns NIL. However, `(#j:console:log "test")` does work.

This one, together the lambda list, will be useful to get a more friendly REPL.

Remove all non determinism from the build process. - [ ] Uses `SOURCE_DATE_EPOCH` env variable in the `compilation-notice` https://reproducible-builds.org/specs/source-date-epoch/

This would ease development and simplify bootstrapping process. The key is to avoid collisions with the host system. This can be achieved with package-renaming as SBCL does, prefixing symbols or...

Try to make sense of the JS stack traces

2

It would be nice to map the JS stack trace to something that JSCL can understands, converting JS identifiers back to the Lisp symbols.

Integrate changes from Vladimir Mezentsev

1

I was sent some contributions to the email from this person with contributions to JSCL. - https://github.com/vlad-km/klib - https://github.com/vlad-km/moren - https://github.com/vlad-km/jscl-chrome-extension The repositories contain code related to DOM manipulation, a...

This is part of designing a clear JS API for jscl, but I keep it here as an example of usage and a project that could add support for jscl:...

JSCL can be used with the REPL right now, but it is not easy to distribute your own code based on it. We need to implement a way to compile...

There is a limitation now to use package during bootstrapping. The `in-package` macro sets `*package*` both at compile-time and load-time. `load` and `compile-time` are supposed to bind `*package*` so a...

This fails for local documents in (at least) some versions of chromium.