What's Changed

• Enable perla commands in interactive in #37
• Static files updates in #38
• Static file improvements in #39
• Handle Ctrl + C and Ensure exit... exits... #25
• Static Files Copy Filters #27
• mounted file's filepath is not preserved #31
• Fix static files directories #33

Full Changelog: v0.12.1...v0.13.0

Fixes a particular issue with TSX projects, they were not accepting the tsconfig options correctly thus failing to be served

This was an interesting release to work with, firstly I thought it would be nearly impossible to make it worth seamlessly at dev time and at build time thankfully esbuild accepts a file via stdin and with some slight changes to the importJS middleware we are able to serve these files and compile them on the fly with esbuild and since esbuild is written in go, it takes mere milliseconds to compile a single file, at this point my code logic is perhaps slower than esbuild

Check CliWrap I really love to work with when dealing with external processes, otherwise I would be in a lot of pain dealing with calling the fable/esbuild process be sure to check it, it's amazing!

This release enables json imports, given that esbuild supports json files as default modules we added a simple middleware that transforms a json request into module with a default export you will be able to use them freely

Ahh quick fix... I fixed single file binaries and broke the tool... here's the fix tested on both the tool and the single file binaries

it's hard to catch runtime issues :P

Here's the fix

        let assemblyLoc =
          Path.GetDirectoryName(Reflection.Assembly.GetEntryAssembly().Location)

        if String.IsNullOrWhiteSpace assemblyLoc then
          Path.GetDirectoryName(Process.GetCurrentProcess().MainModule.FileName)
        else
          assemblyLoc

fix #18 and #19
Self contained single file deploys should work the same as the dotnet tool, for livereload.js and worker.js
Also set System.Text.Json to v6+ to fix a json parsing issue in the .NET 5 version.

Binaries are .NET6 while the dotnet tool allows .NET6 and .NET5

Fix the document query string, I forgot to save the file before publishing... I will setup CI eventually...

CSS HMR is here, I don't have JS HMR thought yet but at least if you're using CSS imports this one is for you

Finally fixed #1 via #16 you are now able to import CSS files right within your code, the resulting css file will be injected at dev time and replaced at build time, so you will have everything you need to have in place

This Release adds #5 which is something that we'd certainly like to have when we're developing stuff this of course opens the road for new cool stuff to build on top of it.

Feel free to give it a try and bring up the feedback!