Kevin Upton

Problems with v4.0.0-0 Webpack version 4.0.1 ``` at-loader]: Child process failed to process the request: TypeError: compiler.createWatchProgram is not a function [0] at createWatch (E:\xampp\htdocs\flinch-frontend\node_modules\awesome-typescript-loader\src\checker\runtime.ts:144:19) [0] at processInit (E:\xampp\htdocs\flinch-frontend\node_modules\awesome-typescript-loader\src\checker\runtime.ts:312:11) [0]...

This would definitely speed things up for us. We run a compile anyway before doing the verification, and need to go through and verify many contracts.

👍 🥇

Ok the solution was because of the way the file was named. I assumed that it would just look at the file contents and if there is a sops then...

is it possible to change this pattern at all ? so it can be `.secrets?.yaml$`.

That is the only thing that this plugin needs. Some better syntax highlighting (remix level). Once it has achieved that, it is by far the best solidity dev environment. 🙏...

> One thing I like about remix is the error highlighting but might be hard to implement as it only shows after compiling the contract I notice that the vscode...

> Hey, @ajianggood @kevupton! When saying like remix, do you mean the colour scheme, or something else? A concrete example might help a lot. @SerCeMan Here is an example of...

@TkDodo I ran some tests and the first render cycle does appear to be fetching:  Using this code: ```ts const useTest = () => { const query = useQueryOptions(()...

yeh ok awesome, will take a look into this one more and see what we can do 🙏