dprint
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.
dprint
-
My opinion about opinionated Prettier: π
Currently, I am using ESLint for formatting of basic things like spacing and quotes. However, those rules were deprecated with v8.53.0 and moved to @stylistic/eslint-plugin. But they recommend Prettier or dprint.
- Oxlint β written in Rust β 50-100 Times Faster than ESLint
-
How do I stop Prettier from de-structuring object properties onto separate lines?
Prettier is opinionated. dprint is highly configurable.
-
Rome v12.1: a Rust-based linter formatter for TypeScript, JSX and JSON
I mean, I know I am a bad person because of those long names, but that is how life goes sometimes! And the blank line there at the top is just very important to like, catch one's breath, while reading this code.
(I'm really just posting this in the hopes that somebody will throw me a "Bro, just use hpstrlnt, it totally lets you configure that!" -- I have not actually tried Rome to see if it does (it's Monday morning and I'm not quite ready to be disappointed again...))
[1]: dprint is good, and I recommend it as the best code formatter I currently know of: https://dprint.dev/
- Is there an extension for forcing a code style?
- What would you rewrite in Rust?
-
What's the best way to generate code?
If it's something in the vein of one of those things then, worst case, you generate the code first, then run it through something like dprint.
- Ask HN: Alternatives to Prettier?
- dprint β Code Formatter
-
Announcing Rome Formatter
Why not compare Rome formatter to the actual competition, https://dprint.dev/ ?
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?
prettier - Prettier is an opinionated code formatter.
react-native - A framework for building native applications using React
nvim-lspconfig - Quickstart configs for Nvim LSP
semantic-release - :package::rocket: Fully automated version management and package publishing
dotfiles - π¨π»βπ» My dotfiles including Neovim Lua config, ZSH with zinit plugin manager & powerlevel10k prompt
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
deno - A modern runtime for JavaScript and TypeScript.
changesets - π¦ A way to manage your versioning and changelogs with a focus on monorepos
apriori-rs - Apriori for association rule mining with Python bindings π¦π
helmfile - Deploy Kubernetes Helm Charts
deno_lint - Blazing fast linter for JavaScript and TypeScript written in Rust
Poetry - Python packaging and dependency management made easy