serialviz
semver
serialviz | semver | |
---|---|---|
2 | 722 | |
5 | 7,026 | |
- | 0.6% | |
0.0 | 0.6 | |
almost 2 years ago | 9 days ago | |
TypeScript | ||
Apache License 2.0 | - |
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.
serialviz
-
Vite 3.0
For my simple app, one-line calls to ESBuild in package.json seem good enough. I run everything using 'npm run dev' or 'npm run build'. See [1].
I suppose it wouldn't scale if the app got too big and complicated.
[1] https://github.com/skybrian/serialviz/blob/main/package.json
-
Raspberry Pico-based 100-Msps logic analyzer
Nice! Looks like the protocol between the Pico and the Windows software is quite simple. Porting it to another OS shouldn't too hard.
Here's an unusual approach to portability for this kind of software: since Chrome supports Web Serial, a web app could do the UI and then it would be portable across operating systems (though still Chromium specific) with no software to install (assuming you already have Chrome or Edge).
Along those lines, I wrote a little web app that plots CSV data from a microcontroller board (which happens to be a Pico). There's not a lot to it, but I like it better than the Arduino plotter and it might be useful as an example:
https://github.com/skybrian/serialviz
semver
-
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
-
First purchase advice
All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)
What are some alternatives?
logicanalyzer - 24 channel, 100Msps logic analyzer hardware and software
react-native - A framework for building native applications using React
sigrok-pico - Use a raspberry pi pico (rp2040) as a logic analyzer and oscilloscope with sigrok
semantic-release - :package::rocket: Fully automated version management and package publishing
gbs-control
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
helmfile - Deploy Kubernetes Helm Charts
Poetry - Python packaging and dependency management made easy
TermuxBlack - Termux repository for hacking tools and packages
fswatch - A cross-platform file change monitor with multiple backends: Apple OS X File System Events, *BSD kqueue, Solaris/Illumos File Events Notification, Linux inotify, Microsoft Windows and a stat()-based backend.
keep-a-changelog - If you build software, keep a changelog.