Daniel Mahon

@montanaflynn you can just replace the top and bottoms colors with whatever `background` you would like: ```jsx {content} ```

So I just tried setting the schema to itself and it worked (surprisingly), no more errors... and no need for a blank file. `# yaml-language-server: $schema=./[current file].yaml` **build.yaml** ```yaml #...

folders using `cloudinary prefix` does not work, I just pushed a fix, basically just copies what CloudinaryImage (singular) was doing

My current solution for an esm module built from esbuild is to update `node-with-require-overrides.js` and use `patch-package` https://github.com/nrwl/nx/pull/10414#issuecomment-1369314024 ```js // node-with-require-overrides.js line 19 // require(fileToRun); import(fileToRun).catch((error) => { console.error('Error importing...

+1

This didnt work for me, same result as --open, only a single device (random) responds, the paths are identical as well