Dustin Getz

I fixed it by using the [Modnakasta fork to process url fragments](https://github.com/modnakasta/pushy), providing a custom `:processable-url?` predicate to ignore urls with fragments (thus not calling preventDefault), and also passing an...

Here's the externs I just created, "works on my machine", I am probably missing some things. Pasting here as a starting point for the next guy who comes along. ```...

Also `document`

This approach forces a choice between fragment navigates and html5 navigates. If the flag is not set, pushy should let the native event through unhandled (no dispatch). It should not...

boot watch --help documents the regex pattern for the watch

i solved this by only having package.json in resource-paths and then running "cd target; yarn" after the resources are copied (assuming node_modules was the problematic resource)

`!` there is `hyperfiddle.rcf/tap`, which used to be `hyperfiddle.rcf/!`

It's the standard deps + shadow-cljs boot sequence

Here is another example, a missing npm dep causes shadow build to fail but the calva connect sequence continues in failed state ``` ; Evaluating 'afterCLJReplJackInCode' (do (require 'user) (user/main))...

* If I use the simple "deps.edn" boot sequence and run shadow via the REPL API, the calva repl prompt is correctly printed once, per the below paste. * However...