denon VS runner

{ "$schema": "https://deno.land/x/[email protected]/schema.json", "scripts": { "start": { "cmd": "deno run main.js", "desc": "start server", "tsconfig": "tsconfig.json", "importmap": "importmap.json", "allow": [ "net", ] } } }

Hey, I found an an issue in the denon repo, but it looks like there aren't any fixes for Deno v1.7.1 right now. However, for the time being, I advise you to add the --watch flag to Deno run and it will also rerun your app on any changes.

Hello. Yes, you get it somewhat right. Japa is way lighter than Jest and Vitest. The main difference is that Japa is more focused on backend applications and libraries and therefore we will be creating plugins in that space. For example: I see Vitest team focusing more on creating plugins specific for Vue, or React components testing, on the other hand, you can expect us to create plugins for testing backend apps written in Fastify, Nest or AdonisJS. > But how about mocking modules as Jest can do and other mock related functionality? Currently, there is no way of mocking modules. I think even Jest is struggling to get mocking work with ESM, because of the internal architecture of ES modules. However, if you can [kick start a discussion](https://github.com/japa/runner/issues/new) in issues, then we can surely talk about how to approach mocks with Japa. > I'm writing a library and I don't have a file watcher, so it would be nice for Japa to have instructions or better to have a plugin for file watcher. Sure, lemme write a guide on same tonight.