napi-rs
Clippy
Our great sponsors
napi-rs | Clippy | |
---|---|---|
35 | 120 | |
5,477 | 10,755 | |
4.7% | 1.9% | |
9.6 | 10.0 | |
7 days ago | 5 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | 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.
napi-rs
- Napi: Build compiled Node.js add-ons in Rust
- Napi.rs, framework for building pre-compiled Node.js addons in Rust
-
Electrons Are Fast, So Can Be Electron – How to Optimize Electron App Performance
Napi-rs
- 🚀 GoRules Zen Engine: Rules Engine for Node.js
-
What's the "modern" way of creating a native addon for Node.js?
Thanks! This seems pretty official. I do really like what I saw from https://napi.rs/ where you just throw a "#[napi]" macro on and it works. Do you know if there's a Node API equivalent C/C++ workflow or tool that does something similar? I think the https://github.com/nodejs/webidl-napi is kinda what I'm looking for but it's archived.
- 🚀 GoRules Zen Engine: Cross-platform rules engine written in Rust
-
Equivalent to wasm-pack for nodejs C FFI?
Does it need to be Neon? From what I've read, there's something about its design that allows napi-rs to achieve better performance in some situations.
-
Node & Rust: Friendship Forever. The NAPI-rs Way.
NAPI-RS is a framework for building pre-compiled Node.js addons in Rust.
-
Write SDK “base” in Rust, wrap in other languages?
For example, they list PyO3 for Python (see also maturin for packaging), NAPI-RS for Node.js, and Rutie for Ruby.
- NAPI-RS 3.0 RFC is ready; come and join the discussion
Clippy
-
More than you've ever wanted to know about errors in Rust
I couldn't find it in the API guidelines either. From what I understand, the idea is that any trait bounds, which includes generic type parameter bounds and lifetime bound on a type (struct or enum) would be repeated back in the impl block
there is a nice discussion on this issue here: https://github.com/rust-lang/rust-clippy/issues/1689
-
New clippy lint: detecting `&mut` which could be `&` in function arguments
You should not blindly follow clippy lints. They are sometimes wrong. Another example https://github.com/rust-lang/rust-clippy/issues/9782 .
- Let else will finally be formatted by rustfmt soon
-
My deduplication solution written in Rust beats everything else: casync, borg...
I often write () = f() to assert that f() is unit. Unfortunately clippy warns on such code ( https://github.com/rust-lang/rust-clippy/issues/9048 ). There are very recent pull requests for this bug, so hopefully this bug will be fixed very soon. But meanwhile I invented this workaround: [()] = [f()] :)
-
Any open source projects willing to take in juniors?
Apart from running clippy on many projects being essential, clippy is also an exceptionally welcoming project, no matter your prior knowledge.
-
Any new Opensource projects in (rust) looking for contributors. I want to start my journey as an OSS contributor.
clippy is a great place to get started :) though it isn't exactly new.
-
I want to contribute in a big project
clippy is also pretty compiler-adjacent and unlike rust-analyzer uses rustc's internal APIs. Don't let the size of the code base scare you off! It's actually feasible for a newcomer to contribute even such a substantial change as a new lint, and we have issues labeled as "good first issue" that come with mentorship, so you don't need to go it alone.
-
rustc-plugin: A framework for writing plugins that integrate with the Rust compiler
Yes, you could use it to write a lint. Although you might find it easier to just fork Clippy and add your own lints to their existing framework.
-
Reading Rust
Check out the readme for more information.
-
Rust Tips and Tricks #PartOne
They are two of my favorite Rust tools. If you haven’t tried them yet, I highly recommend giving them a try. Clippy can detect various lints in your code and guide you towards writing more idiomatic code. To install Clippy, simply run rustup component add clippy, and to run it within your workspace, execute cargo clippy. For more details, visit Clippy’s GitHub repository.
What are some alternatives?
canvas - High performance skia binding to Node.js. Zero system dependencies and pure npm packages without any postinstall scripts nor node-gyp.
rustfmt - Format Rust code
wasmer-go - 🐹🕸️ WebAssembly runtime for Go
vscode-rust
node-canvas - Node canvas is a Cairo backed Canvas implementation for NodeJS.
rust.vim - Vim configuration for Rust.
benchmark - MikroORM vs TypeORM benchmark of CRUD operations on 10k entities
rust-analyzer - A Rust compiler front-end for IDEs [Moved to: https://github.com/rust-lang/rust-analyzer]
PyO3 - Rust bindings for the Python interpreter
Rust for Visual Studio Code
typescript-runtime-type-benchmarks - 📊 Benchmark Comparison of Packages with Runtime Validation and TypeScript Support
intellij-rust - Rust plugin for the IntelliJ Platform