coderaiser
coderaiser
Could you please get rid of `punycode` in CommonJS version of `node-fetch`? It crashes on node v21:
You can also switch to 🐊[**Putout**](https://github.com/coderaiser/putout) code transformer, it has support of: - ✅ [configuration](https://github.com/coderaiser/putout#-configuration); - ✅ [declarative API](https://github.com/coderaiser/putout#-plugins-api) based on 🦎[**PutoutScript**](https://github.com/coderaiser/putout/blob/master/docs/putout-script.md#-putoutscript) - ✅ simplest possible [testing](https://github.com/coderaiser/putout/tree/master/packages/test#putouttest-); - ✅ good...
If I understand correctly it is already possible with help o Node API methods: - [`eslint.calculateConfigForFile()`](https://eslint.org/docs/latest/integrate/nodejs-api#-eslintcalculateconfigforfilefilepath); - [`eslint.lintText()`](https://eslint.org/docs/latest/integrate/nodejs-api#-eslintlinttextcode-options); The only thing to remember is count of passed rules can vary...
> So, I think writing to a different file from a rule is a dangerous use case -- one of the implicit guarantees of ESLint is that rules won't have...
- ✅ [client](https://github.com/cloudcmd/dword/blob/master/assets/index.html) - ✅ [server](https://github.com/cloudcmd/dword/blob/master/bin/dword.js)
Looks like the reason is naming.
Good idea for a PR :)
Any progress on this? Or ideas of how it can look like?
That is strange https://hub.docker.com/r/coderaiser/cloudcmd/tags
Yes, here is examples https://github.com/cloudcmd/theme