rusty_v8
semver
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.
rusty_v8
-
Ask HN: What Are You Building?
I'm building Lagon, an open-source [1] runtime and platform that allows developers to run TypeScript and JavaScript serverless functions at the Edge, close to users. The runtime uses V8 Isolates and is written from scratch using Rust and rusty_v8 [2], Deno's Rust bindings for V8.
[1] https://github.com/lagonapp/lagon
[2] https://github.com/denoland/rusty_v8
-
WasmEdge
Not to denigrate your work, it's good what you're working on... but I can create JS APIs in Rust with native V8 bindings, too: https://github.com/denoland/rusty_v8/blob/main/examples/proc...
-
based on recent struggles
For more futuristic stuff, check out Typescript native Deno and rustbased v8
-
Dune: A new JavaScript and TypeScript runtime
No, that will be rusty_v8
-
Create Your Own JavaScript Runtime
V8 Rust Bindings Examples — Rusty V8 GitHub
-
Deno 1.25
Can Deno be embedded in a larger Rust application? I know I can embed v8 directly https://github.com/denoland/rusty_v8 but I wish I could use other parts of Deno.
In particular, I wish I could write a Tokio async program in Rust, and load plugins using deno, and have this work seamlessly
- We really need an ARM build.
- Deno is on MDN
-
Deno v1.10 Released
> git clone https://github.com/denoland/rusty_v8.git denoland/rusty_v8
semver
-
Why write a library?
Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.
-
Node package managers (npm, yarn, pnpm) - All you need to know
npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.
-
Snyk CLI: Introducing Semantic Versioning and release channels
We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.
-
Master the Art of Writing and Launching Your Own Modern JavaScript and Typescript Library in 2024
Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…
-
Testing Our Tasks
The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?
-
What is Semantic Versioning and why you should use it for your software ?
For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org
-
Neovim v0.9.5 Released
I believe neovim follows semantic versioning. https://semver.org/
-
Semver 2.0.0 Released
Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.
https://github.com/semver/semver/releases
What are some alternatives?
v8-runtime-tutorial - Source code for the tutorial series
react-native - A framework for building native applications using React
ninja_gn_binaries
semantic-release - :package::rocket: Fully automated version management and package publishing
deno - A modern runtime for JavaScript and TypeScript.
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
zx - A tool for writing better scripts
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
astrodon - Make Desktop apps with Deno 🦕
helmfile - Deploy Kubernetes Helm Charts
authcompanion - [Deprecated] navigate instead to version 2 of AuthCompanion
Poetry - Python packaging and dependency management made easy