mam_mol
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.
mam_mol
- $mol β fastest reactive micro-modular compact flexible lazy UI web framework
-
Reactive Tech from the Future
And for those who, for some reason, are not yet ready to completely switch to the $mol framework, we have prepared several independent micro-libraries:
-
Reactive DOM
Do you want to try ReactiveDOM in action right now? I published a prototype of the polyfill $mol_wire_dom.
-
Reactive JSX
To do this, we will first take $mol_jsx, which is the same as E4X creates real DOM nodes, not virtual ones:
-
Really Reactive React
Well, let's cure the patient, and at the same time show the ease of integration of the reactive library $mol_wire into a completely foreign architecture.
-
Perfect Reactive Dependency Tracking
We have omitted some methods here. The complete set can be found in the sources $mol_wire_set.
-
Reactivity Practicality in Popular JS Libraries
As you can see, proceduralism is more popular here, which is also not the most practical approach. And the most practical thing here is Vue. Only $mol is cooler than it, but there is no point in considering it separately as a framework, because it simply uses the $mol_wire library as a circulatory system, and we have already analyzed it earlier.
-
Reactive Interactions with External Systems
$mol_wire_sync makes any API synchronous.
- $mol Cheat Sheet by Milis (2 pages) #programming
- $mol - Reactive micro-modular UI framework. Very simple, but very powerful!
semver
-
Git commit helper: add emojis to your commits
Using Conventional Commits β as a standard for your commit messages, makes Semantic Versioning π as easy as can be, with tools like Conventional Changelog π Standard Version π and Semantic Release π¦π
-
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/
What are some alternatives?
mol - $mol - fastest reactive micro-modular compact flexible lazy ui web framework. [Moved to: https://github.com/hyoo-ru/mam_mol]
react-native - A framework for building native applications using React
tree.d - Tree - simple fast compact user-readable binary-safe extensible structural format
semantic-release - :package::rocket: Fully automated version management and package publishing
marked.hyoo.ru - MarkedText - simpliest usefull lightweight markup language, better alternative to MarkDown
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
react-redux-realworld-example-app - Exemplary real world application built with React + Redux
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
vscode-language-tree - VSCode tree format support
helmfile - Deploy Kubernetes Helm Charts
herina - A toolkit providing dynamic ability for React Native App.
Poetry - Python packaging and dependency management made easy