awesome-eslint
shared-everything-threads
awesome-eslint | shared-everything-threads | |
---|---|---|
5 | 2 | |
4,124 | 18 | |
- | - | |
5.0 | 7.2 | |
20 days ago | 5 days ago | |
WebAssembly | ||
Creative Commons Zero v1.0 Universal | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-eslint
-
Prettier $20k Bounty was Claimed
[2] https://github.com/dustinspecker/awesome-eslint#plugins
-
What are good ways to speed up the small little things when developing? Like typing this `${}` or the function definition of a react component? How can I use shortcuts in VS code, or are there any other tools? Pls also tell if you solved other small problems for yourself.
There's a big world of Awesome ESLint plugins.
-
What is the best way to maintain react js coding standard?
ESLint is sort of the go-to code quality/style enforcer, here's a repo that contains all the popular configurations from large open source projects as well as well known companies.
-
How to setup Prettier, ESLint, Husky and Lint-Staged with a NextJS and Typescript Project
3. Install additional configs and plugins in order to extend the functionality of our linter. These the are multiple configs and plugins that I use for every project. ( you can add or exclude anything that you don't want from this setup ). Here is a list of things you can add.
-
¿Qué es Linting y ESLint?
Awesome ESLint: Una lista de configuraciones, parsers, plugins y otras herramientas para mejorar tu propia configuración de ESLint.c
shared-everything-threads
-
Prettier $20k Bounty was Claimed
The roadmap I linked above. The WASI folks have done a poor job at communicating, no doubt, but I'm surprised someone like yourself literally building a competitor spec isn't following what they are doing closely.
Just for you I did some googling: see here[0] for the current status of WASI threads overall, or here[1] and here[2] for what they are up to with WASI in general. In this PR[3] you can see they enabled threads (atomic instructions and shared memory, not thread creation) by default in wasmtime. And in this[4] repository you can see they are actively developing the thread creation API and have it as their #1 priority.
If folks want to use WASIX as a quick and dirty hack to compile existing programs, then by all means, have at it! I can see that being a technical win. Just know that your WASIX program isn't going to run natively in wasmtime (arguably the best WASM runtime today), nor will it run in browsers, because they're not going to expose WASIX - they're going to go with the standards instead. so far you're the only person I've met that thinks exposing POSIX fork() to WASM is a good idea, seemingly because it just lets you build existing apps 'without modification'.
Comical you accuse me of being polarizing, while pushing for your world with two competing WASI standards, two competing thread creation APIs, and a split WASM ecosystem overall.
[0] https://github.com/bytecodealliance/jco/issues/247#issuecomm...
[1] https://bytecodealliance.org/articles/wasmtime-and-cranelift...
[2] https://bytecodealliance.org/articles/webassembly-the-update...
[3] https://github.com/bytecodealliance/wasmtime/pull/7285
[4] https://github.com/WebAssembly/shared-everything-threads
-
WASI Support in Go
The answer is: it's complicated. Which is most of the time the answer in the WASI world.
For this case it's complicated because some runtime supports https://github.com/WebAssembly/threads which mostly contains things like the spec for atomic but not the actual "threads" specs and then some runtimes (i.e wasmtime) also supports https://github.com/WebAssembly/wasi-threads which is one version of the threads. But a new proposal came into play https://github.com/abrown/thread-spawn so ... it's complicated.
What are some alternatives?
github-cheat-sheet - A list of cool features of Git and GitHub.
prettier-plugin-curly - Prettier plugin to enforce consistent brace style for all control statements. 🥌
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
proposals - Tracking WebAssembly proposals
prettier-rpc - Single-file build of prettier with JSON-RPC communication
wasi-threads
jco - JavaScript tooling for working with WebAssembly Components
biome - A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter and linter, usable via CLI and LSP.
vscode-react-javascript-snippets - Extension for React/Javascript snippets with search supporting ES7+ and babel features
awesome-standard - Documenting the explosion of packages in the standard ecosystem!