fzy.js
parcel
fzy.js | parcel | |
---|---|---|
1 | 171 | |
147 | 43,169 | |
- | 0.2% | |
0.0 | 9.5 | |
3 months ago | about 19 hours ago | |
JavaScript | JavaScript | |
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.
fzy.js
-
GTK 4.2.0 is out! New GL renderer, input hints, and a whole new API reference
Some feedback about the new documentation: - Big logo on sidebar leaves less space for actual links - The font pairing (RedHat/Noto, sans-serif/serif) is a bit weird, you might as well use RedHat (Text and Display) for everything if you're gonna include both. - Search results are bad, replacing the stemmer altogether with fuzzy searching would be way more useful (e.g. the fzy algorithm is great) - I'd be happy to help, but I've taken a look at the repo and your build system and it all seems quite dated from a javascript development perspective, I'd at least bundle all the files in a single one and avoid using globals in multiple files by using a import/export syntax. If you're interested let me know I can open a PR with the adjustments above.
parcel
-
How and why do we bundle zx?
At first we wanted to just get rid of all the helper utilities. Keep only the kernel, but this would mean a loss of backward compatibility. We needed some efficient code processing instead with recomposition and tree-shaking. We needed a bundler. But which one? Our testing approach relies on targets, not sources. We rebuilt the project frequently, speed was critical requirement. In essence, we chose a solution from a couple of among all available alternatives: esbuild and parcel. Esbuild won. Specifically in our case, it proved to be more productive and customizable.
-
DEMO - Voice to PDF - Complete PDF documents with voice commands using the Claude 3 Opus API
It runs using Parcel, very simple and easy to setup. The app has 3 files:
-
Getting started with TiniJS framework
Homepage: https://parceljs.org/
-
React Server Components Example with Next.js
In the Changelog Podcast episode referenced above, Dan Abramov alluded to Parcel working on RSC support as well. I couldn’t find much to back up that claim aside from a GitHub issue discussing directives and a social media post by Devon Govett (creator of Parcel), so I can’t say for sure if Parcel is currently a viable option for developing with RSCs.
-
JS Toolbox 2024: Bundlers and Test Frameworks
Parcel 2 emphasizes a zero-configuration approach to bundling web applications. It's a powerful tool that offers a hassle-free developer experience, focusing on simplicity and speed.
-
Build a Vite 5 backend integration with Flask
Once you build a simple Vite backend integration, try not to complicate Vite's configuration unless you absolutely must. Vite has become one of the most popular bundlers in the frontend space, but it wasn't the first and it certainly won't be the last. In my 7 years of building for the web, I've used Grunt, Gulp, Webpack, esbuild, and Parcel. Snowpack and Rome came-and-went before I ever had a chance to try them. Bun is vying for the spot of The New Hotness in bundling, Rome has been forked into Biome, and Vercel is building a Rust-based Webpack alternative.
-
What is JSDoc and why you may not need typescript for your next project?
Parcel
-
Building Node.js applications without dependencies
I’ve tried something similar on the frontend side: I decided to build a UI for Ollama.ai using only HTML, CSS, and JS (Single-Page Application). The goal is to learn something new and have zero runtime dependencies on other projects and NPM modules. Only Node and Parcel.js (https://parceljs.org/) are needed during development for serving files, bundling, etc. The only runtime dependency is a modern browser.
Here's what I have found so far:
- JavaScript (vanilla) is a viable alternative to React.js
-
11 Ways to Optimize Your Website
Besides Webpack, there are many other popular web bundlers available, such as Parcel, Esbuild, Rollup, and more. They all have their own unique features and strengths, and you should make your decision based on the needs and requirements of your specific project. Please refer to their official websites for details.
-
Bun vs Node.js: Everything you need to know
In the Node.js ecosystem, bundling is typically handled by third-party tools rather than Node.js itself. Some of the most popular bundlers in the Node.js world include Webpack, Rollup, and Parcel, offering features like code splitting, tree shaking, and hot module replacement.
What are some alternatives?
flexsearch - Next-Generation full text search library for Browser and Node.js
vite - Next generation frontend tooling. It's fast!
LeaderF - An efficient fuzzy finder that helps to locate files, buffers, mrus, gtags, etc. on the fly for both vim and neovim.
gulp - A toolkit to automate & enhance your workflow
node-gtk - GTK+ bindings for NodeJS (via GObject introspection)
esbuild - An extremely fast bundler for the web
Next.js - The React Framework
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Rollup - Next-generation ES module bundler
Snowpack - ESM-powered frontend build tool. Instant, lightweight, unbundled development. ✌️ [Moved to: https://github.com/FredKSchott/snowpack]
tsdx - Zero-config CLI for TypeScript package development
create-react-app - Set up a modern web app by running one command.