Jan Špaček
Jan Špaček
The issue is that we use `esbuild` in `chisel apply` to bundle user code into a single module (if `modules = "node"`), but the bundler cannot resolve an import of...
The issue is demonstrated in the test `cli/tests/lit/http-import.node` from #1556.
The problem is that we need a "request context" to assign model operations to their request. For example, when mutating an entity in database, we need to check that the...
`chisel apply --type-check` rejects this code, but `chisel apply` accepts it, because typechecking is disabled by default. It matters because it means that users are less likely to hit this...
Ideally, `chisel dev` would keep track of all modules in the module map. This requires serious refactoring of modules in `chisel apply`.
In #1618, when I connect with the inspector, I am at least able to add breakpoints to the transpiled JavaScript and step through that code. But if I understand correctly,...
That works too  But I have to click on the "Open dedicated DevTools for Node" link in chrome://inspect, otherwise Chrome does not show the "Node" tab inside of the...
At least in Deno mode, this also works without "DevTools for Node", after adding files from the filesystem into the workspace. 
Yes, I think that this is one reason for performing the database work in `chisel apply` rather than in `chiseld`: if the apply gets broken and `chiseld` does not start,...
When we talk about reusing the frontend types, do we expect that the frontend and backend share the same code, or just that you can copy-paste your frontend code into...