hammer
parcel
hammer | parcel | |
---|---|---|
9 | 169 | |
232 | 43,122 | |
- | 0.1% | |
3.1 | 9.4 | |
7 months ago | 3 days ago | |
TypeScript | 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.
hammer
-
How to setup a monorepo where building is not necessary for individual packages, just the main one?
NX repositories build slower, drop 1000's of dependencies in your project and has configurations so verbose you need vscode plugins to drive it (also I didn't like that I had to drop in project scaffolding templates to provision new library or application types). I disliked using it so much I went ahead and built this thing https://github.com/sinclairzx81/hammer.
-
What is your workflow when developing with typescript?
My development workflow is principally based on https://github.com/sinclairzx81/hammer which is esbuild tooling I wrote myself. I think these days, if you're using TS and want the rapid development workflow, anything that is leveraging esbuild or swc under the hood will be a good thing to pick. So Vite ticks the esbuild box.
-
Best tooling for Typescript now days
I use https://github.com/sinclairzx81/hammer. It provides watch / reload workflows for both node and browser development and it scales from single applications into large mono repository projects. It takes one dependency (esbuild) and needs next to no configuration to use.
- Typescript monorepo with component library help!
-
Advice on build scripts and tooling
I gave up on community build tooling and ended up rolling my own tools. https://github.com/sinclairzx81/hammer. It's difficult to find any tooling in the community that does all the things you may need it to. I found by investing the time into developing tools to align to my workflows, I'm free to modify those tools without getting bogged down in ecosystem plugins, or arcane configurations, or whatever else.
-
Practising typescript without framework?
If you just want to get going, you can try https://github.com/sinclairzx81/hammer, (disclaimer I wrote this), or https://parceljs.org/ . Both are zero configuration and will allow you to add in frameworks as you need them (rather than relying on the kitchen sink project bootstrappers like create-react-app).
- Hammer: A build tool for node and browser applications
- Hammer: Using esbuild to create better tools for the web
parcel
-
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.
-
JavaScript Gom Jabbar
There are projects attempting to do more things. I've really enjoyed Parcel (https://parceljs.org). But it won't handle things like linting or unit testing, which you may or may not want. Vite is also pretty popular (https://vitejs.dev/), and it has a test runner.
Thing is, most of the problems described in the post aren't related to low-JS front-end libraries like HTMX or alpine. You can write React without a linter, bundler, build tool, unit testing, or linting. But with any of these projects at scale, you start wanting more:
- If you want to write unit tests in JS, you need to choose a test runner (probably Jest or Vitest -- until the built-in node testing module becomes more common).
- If you want linting, you need a linter (probably Eslint). If you want type safety, you need a type checker (probably Typescript).
- If you want to create smaller JS files to ship to production and to automatically handle assets, you need a bundler.
- If you want to use new language features while supporting old browsers, you need polyfills.
- If you want to use all these things together, you need something to bring it together (like Webpack).
So it really depends what you need! You may not need any. But as you can imagine, in many professional projects with multiple developers it's very nice to have unit tests, linting, and type checking :) (And you start caring about end-user performance a lot more, in which case optimizing the shipped bundle is important.)
Take all that, and then compare to a language like Rust, which has most of the "ecosystem stuff" built-in. In Rust, you get the test runner, the linter, dependency manager, type checker, and documentation tool all included. Easy! Thankfully, Rust doesn't have to care about whether users support modern language features (because it compiles down to lower code ahead of time), or whether the binary shipped to the client is optimally organized for downloading immediately over the internet.
It's a problem in JS because A) you have to care about more problems than many other languages since JS needs to load instantly over the wire in a web browser, and B) there is a huge amount of choice and not a lot of standardization in web tools. (And what standardization there is (Node, npm), there are still competitors trying to even further reduce the pain points.)
I think that in ten more years, we'll be in a better place, because there is push back (like this post!) against these problems, which will encourage more tools trying to solve the explosion of tools. Which seems counterintuitive, but these tools were created to solve very real problems. So I see it as a pendulum which has swung too far, but will likely swing back to a more balanced place. And you see that with tools like Vite gaining popularity.
What are some alternatives?
lightproxy - đź’Ž Cross platform Web debugging proxy
vite - Next generation frontend tooling. It's fast!
sidewinder - Type Safe Micro Services for Node
gulp - A toolkit to automate & enhance your workflow
bundlejs - An online tool to quickly bundle & minify your projects, while viewing the compressed bundle size, all running locally on your browser. A quick and easy way to bundle, minify, and compress (gzip and brotli) your ts, js, jsx and npm projects all online, with the bundle file size.
esbuild - An extremely fast bundler for the web
rules_nodejs - NodeJS toolchain for Bazel.
Next.js - The React Framework
blog.cnc4me.org - Excerpts from the development of the virtual Fanuc Macro B runtime and the accompanying Macro Playground
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.
wmr - 👩‍🚀 The tiny all-in-one development tool for modern web apps.
Rollup - Next-generation ES module bundler