semantic-release
vite
Our great sponsors
semantic-release | vite | |
---|---|---|
75 | 786 | |
19,768 | 64,595 | |
1.6% | 1.8% | |
9.4 | 9.9 | |
5 days ago | 5 days ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
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.
semantic-release
- alacritty-themes not working any more!!!
- Announcing @ngneat/avvvatars
- Auto versioning?
-
Is it possible to bypass merge queue requirement for a GitHub app without needing admin permissions?
I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.
-
How to set up Commitzen with Husky
Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.
-
Automated release with Semantic Release and commitizen
When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.
- π¦ Effortless Data Quality w/duckdb on GitHub βΎοΈ
-
How I Sliced Deployment Times to a Fraction and Achieved Lightning-Fast Deployments with GitHub Actions
To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.
- Automated Release Notes in Azure Devops
-
What are some examples of good release notes from open source projects that you have come across?
If your projects ar made in javascript and related tools, I'd suggest you to check: semantic-release
vite
-
Approaches to Styling React Components, Best Use Cases
I am currently utilizing Vite:
-
Getting started with TiniJS framework
Homepage: https://vitejs.dev/
-
Use CSS Variables to style react components on demand
Without any adding any dependencies you can connect react props to raw css at runtime with nothing but css variables (aka "custom properties"). If you add CSS modules on top you don't have to worry about affecting the global scope so components created in this way can be truly modular and transferrable. I use this with vite.
-
RubyJS-Vite
Little confused as to why it has vite in itβs name, it seems unrelated to https://vitejs.dev/
-
Ask HN: How do we include JavaScript scripts in a browser these days?
it says in their docs that they recommend Vite https://vitejs.dev/
it goes like this.
1. you create a repo folder, you cd into it.
2. you create a client template using vite which can be plain typescript, or uses frameworks such as react or vue, at https://vitejs.dev/guide/
3. you cd in that client directory, you npm install, then you npm run dev, it should show you that it works at localhost:5173
4. you follow the instructions on your url, you do npm install @web3modal/wagmi @wagmi/core @wagmi/connectors viem
5. you follow the further instructions.
> It seems like this is for npm or yarn to pull from a remote repository maintained by @wagmi for instance. But then what?
you install the wagmi modules, then you import them in your js code, those code can run upon being loaded or upon user actions such as button clicks
> Do I just symlink to the node_modules directory somehow? Use browserify? Or these days I'd use webpack or whatever the cool kids are using these days?
no need for those. browserify is old school way of transpiling commonjs modules into browser-compatible modules. webpack is similar. vite replaces both webpack and browserify. vite also uses esbuild and swc under the hood which replaces babel.
> I totally get how node package management works ... for NODE. But all these client-side JS projects these days have docs that are clearly for the client-side but the ES2015 module examples they show seem to leave out all instructions for how to actually get the files there, as if it's obvious.
pretty much similar actually. except on client-side, you have src and dist folders. when you run "npm run build" vite will compile the src dir into dist dir. the outputs are the static files that you can serve with any http server such as npx serve, or caddy, or anything really.
> What gives? And finally, what exactly does "browserify" do these days, since I think Node supports both ES modules and and CJS modules? I also see sometimes UMD universal modules
vite supports both ecmascript modules and commonjs modules. but these days you'll just want to stick with ecmascript which makes your code consistently use import and export syntax, and you get the extra benefit of it working well with your vscode intellisense.
> In short, I'm a bit confused how to use package management properly with browsers in 2024: https://modern-web.dev/guides/going-buildless/es-modules/
if people want plain js there is unpkg.com and esm.sh way, but the vite route is the best for you as it's recommended and tested by the providers of your modules.
> And finally, if you answer this, can you spare a word about typescript? Do we still need to use Babel and Webpack together to transpile it to JS, and minify and tree-shake, or what?
I recommend typescript, as it gives you better type-safety and better intellisense, but it really depends. If you're new to it, it can slow you down at first. But as your project grows you'll eventually see the value of it. In vite there are options to scaffold your project in pure js or ts.
-
Deploy a react projects that are inside a subdirectories to GitHub Pages using GitHub Actions (CI/CD)
First you have to know that all those react projects are created using Vite, and for each of them, you need change the vite.config.ts file by adding the following configuration:
-
CSS Hooks and the state of CSS-in-JS
CSSHooks works with React, Prereact, Solid.js, and Qwik, and weβre going to use Vite with the React configuration. First, let's create a project called css-hooks and install Vite:
-
Collab Lab #66 Recap
JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite
-
Use React.js with Laravel. Build a Tasklist app
For this full-stack single-page app, you'll use Vite.js as your frontend build tool and the react-beautiful-dnd package for draggable items.
-
Top 10 Tools Every React Developer Needs in 2024
Vite
What are some alternatives?
GitVersion - From git log to SemVer in no time
Next.js - The React Framework
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
parcel - The zero configuration build tool for the web. π¦π
Release It! π - π Automate versioning and package publishing
esbuild - An extremely fast bundler for the web
release-drafter - Drafts your next release notes as pull requests are merged into master.
swc - Rust-based platform for the Web
commitlint - π Lint commit messages
astro - The web framework for content-driven websites. βοΈ Star to support our work!
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles
Rollup - Next-generation ES module bundler