- Apr 18, 2023
-
-
Shachar Itzhaky authored
Instead of `.cjs`; enough with this nonsense.
-
- Apr 12, 2023
-
-
Shachar Itzhaky authored
-
- Feb 01, 2023
-
-
Emilio Jesus Gallego Arias authored
-
- Jan 30, 2023
-
-
Emilio Jesus Gallego Arias authored
-
Emilio Jesus Gallego Arias authored
-
- Jan 24, 2023
-
-
Emilio Jesus Gallego Arias authored
-
Emilio Jesus Gallego Arias authored
- don't rebuild the cli stuff when the frontend/backend changes - make tests work again
-
Emilio Jesus Gallego Arias authored
This is not perfect but it works (and it is much faster). For some reason I couldn't make `fflate-unzip` work with ESBuild, so I've placed a copy and tweaked the exports.
-
Emilio Jesus Gallego Arias authored
This is a large build-time improvement, moreover we can get rid of a lot of troublesome code regarding how to manage assets. `esbuild` has proven a great tool so far. Tested with both backends. We still keep the CLI and the WASM backend on webpack, the idea is to move them to esbuild in subsequent commits. CLI should use a native Coq instead, it is super-slow. We also disabled the `collab` and `ide-project` builds for now, re-adding before merging hopefully. The compatibility story with user .html pages needs to be revised, IMHO as this is a foundation for the LSP backend this is the time to drop support for some patterns we had in the past.
-
- Jan 05, 2023
-
-
Emilio Jesus Gallego Arias authored
-
Emilio Jesus Gallego Arias authored
Borrowed from #275
-
Emilio Jesus Gallego Arias authored
We remove unused / browser `pp2HTML` and `richpp2HTML`, and we move goal printing to coq-manager (for now), as to make the library purely about `Pp.t -> Html` conversion.
-
Emilio Jesus Gallego Arias authored
We will reuse this library from vsCode (and maybe other projects), so it makes sense to put it in its own directory, and maybe even at some point in npm. Along the way, we will cleanup some unused code, and add typing info borrowed from #275
-
- Oct 12, 2022
-
-
Emilio Jesus Gallego Arias authored
This should cleanup the root directory a bit; I've placed the cli files inside `frontend`, but quite a few of these files should eventually move to backend, as it seems to me that they functionality that the "server" should provide, but we can do like this for now and move things to `backend` as we see fit.
-
- Oct 11, 2022
-
-
Shachar Itzhaky authored
There is no longer @jscoq / @wacoq separation in pkgs.
-
Shachar Itzhaky authored
Fixes #297.
-
Shachar Itzhaky authored
Fixes #297.
-
- Oct 05, 2022
-
-
Shachar Itzhaky authored
-
- Oct 03, 2022
-
-
Shachar Itzhaky authored
Removed the backporting discrepancy in package builder.
-
- Oct 02, 2022
-
-
Shachar Itzhaky authored
Changed the calls from JS to be more similar.
-
- Sep 21, 2022
-
-
Emilio Jesus Gallego Arias authored
-
Emilio Jesus Gallego Arias authored
We also move from hacks to a proper config object (which can be properly created in a dynamic top-level context). Also, note that we now use a ES6 map for the routes, this is more convenient to add / remove elements than using the bare object.
-
Emilio Jesus Gallego Arias authored
-
Emilio Jesus Gallego Arias authored
This is rarely used live, and should allow us to make progress towards the common protocol a bit more easy.
-
Emilio Jesus Gallego Arias authored
-
Emilio Jesus Gallego Arias authored
We reorganize jsCoq's source code as to be more modular, in particular we start to place backend files under the `backend` directoy, and frontend files under `frontend`. Code as it now does work, note however that still quite a bit of work is needed. In particular, the headless frontend should get its own directory, the coq-jslib directory should go away, use more types, etc...
-