alias-hq
volta
alias-hq | volta | |
---|---|---|
3 | 84 | |
329 | 9,994 | |
- | 2.1% | |
4.5 | 9.1 | |
6 months ago | 4 days ago | |
JavaScript | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
alias-hq
-
The Native Way To Configure Path Aliases in Frontend Projects
There are multiple libraries available for configuring path aliases in Node.js, such as alias-hq and tsconfig-paths. However, while looking through the Node.js documentation, I discovered a way to configure path aliases without having to rely on third-party libraries. Moreover, this approach enables the use of aliases without requiring the build step.
-
Path Aliases in TypeScript and why you should use them
You could make it work by yourself, but… instead of spending some time figuring out how to do it (feel free to do it if you want or have time for that), I recommend you to check this amazing package (Alias HQ) which is free and basically uses your tsconfig.json or jsconfig.json file to setup everything for you and make really easy to configure all those more advanced needs.
-
[AskJS] Do you use Yarn v2?
Where I personally gave up on trying to use Yarn + PnP for my team's project was folder aliases. We had a few aliases set up using https://github.com/davestewart/alias-hq , so that we could use the same aliases with Node, Jest, and Webpack. That wouldn't work as-is, because again Yarn has to have full control over all package file access, and so it needs to understand what those aliases are. I got stuck trying to figure out how to get those aliases configured with Yarn instead, and gave up on PnP at that point.
volta
- Volta – Fastest Node version manager in Rust
-
Faster Postgres Queries with Cloudflare Hyperdrive and Neon
Your local machine should have Node.js and npm installed. Wrangler CLI requires a Node version of 16.13.0 or later to avoid permission issues.
- The Hassle-Free JavaScript Tool Manager
-
You should be using rtx
For node version management, I highly recommend Volta (not affiliated) - https://volta.sh
-
Volta and NW.js are amazing together
Go to https://volta.sh and install Volta
-
What's New in Node.js 21
Alternatively, a better way to manage Node.js releases on your machine is to use an environment management tool like Volta that can install and switch between multiple versions seamlessly.
-
Best practices for HarperDB projects using TypeScript
To use TypeScript you need Node.js installed, be sure to use the latest LTS version. You can check it by running node -v in your terminal. If you don't have it installed, you can download it here, or use a version manager like asdf, nvm, or even volta.
- Volta – The Hassle-Free JavaScript Tool Manager
- Volta: The Hassle-Free JavaScript Tool Manager
- INSTALLATION
What are some alternatives?
ts-monorepo - Template for setting up a TypeScript monorepo
fnm - 🚀 Fast and simple Node.js version manager, built in Rust
tsdx - Zero-config CLI for TypeScript package development [Moved to: https://github.com/jaredpalmer/tsdx]
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
tsdx - Zero-config CLI for TypeScript package development
nvm - Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
cli - the package manager for JavaScript
nvm for Windows - A node.js version management utility for Windows. Ironically written in Go.
tsconfig-paths - Load node modules according to tsconfig paths, in run-time or via API.
n - Node version management
jest - Delightful JavaScript Testing.
nushell - A new type of shell