To be honest, given the many great and well funded bundlers out there now (when Parcel started there was only webpack and browserify!), I considered whether it was worth continuing the project. But I enjoy working on it and I think I still have things to contribute to this space.

Interactive inverse kinematics: drag end-effectors and the solver works out the joint angles. Multi-tip robots get one gizmo per limb. Tech stack was Grunt Browserify COLLADA but now is Vite TypeScript URDF. 🥳 Try it out and let me know what you think. Thanks!

🚧 WIP PR: “General dependencies & tooling upgrade, remove build warnings” github.com/Adamant-im/adaman… This is a deep maintenance pass across ADAMANT Messenger (PWA Electron): reduce tech debt, kill build/runtime warnings, and align with modern tooling. Why it matters: censorship-resistant privacy software needs a boring, stable foundation. Old tooling = flaky builds, deprecations, security drift, and harder releases. This PR is mostly invisible to users — but huge for reliability. Phase 1 done: baseline type safety Fixed TS 5.7 compilation blockers (chat form, upload flow, utilities). Refined buffer types (Uint8Array) for stricter Blob/DOM requirements safer null-checks around nextTick. Tooling upgrades in motion: • ESLint → v9 Prettier → v3.5 • TypeScript → v5.9.3 Goal: consistent linting, fewer footguns, fewer CI surprises, and a cleaner contributor experience. UI state refresh (part of the WIP): • Vue → 3.6 • Pinia → 3 • Vuetify → 3.8 Plus router / i18n / VueUse updates, and networking/core libs (axios, BigNumber, vue-query). 2026 stack alignment: • Vite → 7.3.0 core plugins • Vitest → 4.0.17 • Capacitor → 8.0.0 (Android platform update) • Electron → 39.2.7 Targets: stable dev/build for web desktop mobile. Crypto wallet plumbing updates: • bitcoinjs-lib → v7, ecpair → v3 • Fix strict runtime validation (“ValiError”) by enforcing bech32 as a string Also tracking upgrades like secp256k1 v5 crypto-browserify as part of the checklist. Build warning cleanup checklist includes: • sourcemap warnings • glob deprecations • deprecated rollup polyfills • browser console warnings • Electron stack upgrade cross-platform smoke tests (Win/macOS/Linux/Android) API/tooling maintenance included too: Upgrading swagger/openapi generators and fixing CLI scripts to match breaking changes — keeping typed API workflows healthy. Status: still a draft / in progress. Current focus: removing initial build blockers after dependency refresh steady verification via test deployments.

I'm still on that Browserify gulp setup.

script tags -> grunt -> gulp -> broccoli -> browserify -> webpack -> ~~parcel~~ -> vite

if you have migrated any less than 3 code bases from browserify, gulp, and or grunt to webpack yngmi

You annual reminder that you should not be using crypto-browserify or any other node or browser port of the crypto API react-native-quick-crypto 👑

Eu lembro que antigamente era horrível ter que lidar com uns 5 browsers diferentes com comportamentos diferentes, lidar com o bower, gulp/grunt, jquery, requirejs, autoprefixer, uglify, browserify, normalize-css... Fora os hacks do IE7, 8, 9... hackernoon.com/how-it-feels-…

v2.0.6用の browserify 作成しました🥸 #Symbol #browserify github.com/mikunNEM/symbol-b…

間違ってはないんだけど browserify がnodeのcjsのエミュレーターとして登場したことや、当初はnpm と bower で棲み分けようとした視点がないと当時の空気感全く追えない気がした qiita.com/im_yoneda/items/cc…

[at]rsbuild/plugin-node-polyfill の中で依存している browserify crypto みたいな名前系のライブラリ、よく脆弱

🔥 Freshly brewed in Tea ✨ node-constants-browserify 📦 TeaRank: 49.03 🔗 GH: github.com/juliangruber/cons… 🍵 Tea: app.tea.xyz/package/node-con… Julian Gruber, thank you for registering on testnet and strengthening open source. One package at a time, we’re redefining how OSS is rewarded. 🔥 Mainnet is coming — OSS will never be the same. 🚀 Tea is the new open source economy. 🌍

简单分享一下个人经历和观点吧，专科毕业，财务出身，然后读了个一年制的水硕转计算机，后来入职微软，现在辞职自创业。 我觉得传统意义上的 junior 和 senior 型没有任何意义了。很多 junior 比那种十多年经验的 senior 要强很多，本质上就是 AI 就是一个很强的 bullshit detector。过去 junior 的标准和现在 junior 的标准或者是 senior 的标准都完全不一样。 我觉得最关键的能力就是和 AI 一样泛化或者是了解多方面问题的能力，而不是只专注于一个领域。未来人能做的事情多很多，所以只专注一个领域没有必要了。举个例子，比如说除了 top10 或者 top50 的公司或团队，研究一些高精尖的领域没有任何意义，比如说云原生，Kubernetes, iOS Native 开发没有很大意义。反而是怎么去架构软件适合跟 AI 协作是一个新的能力。如果一个 junior 有这种视野和能力，那么他们是远超 senior 的。这也是我为什么要前天说，现在真的是过去的阶级被打破了。 举个例子，我刚毕业就入职微软，入职我们团队是 iOS 团队，Outlook iOS，leader 们不到半年就给我了很大的任务，就是改整个 app 的最核心的就是 email editor 和 email renderer。你用微软的 Outlook 基本上就是收发邮件或者是用日历，然后我一个人就去改了非常多很核心的部分。不是因为我厉害，是因为其他人不懂前端，因为邮件的渲染器和编辑器都是前端代码写的。 基本是我一个人把微软 Outlook iOS 和 Android 的邮件渲染器从 JavaScript 和 Browserify 迁移到了 Webpack 和 TypeScript，然后又加了很多更好的架构设计。这东西也不是什么 rocket science，也不是什么高深的科技，就是优秀的工程化。这种 migration 在没有 AI 的时代确实也挺难的，因为你不能把这个 app 搞挂，这是最核心的。很多用户都是那种财富 500 强客户，对吧，也不能让他们不能用手机回邮件，这样的话这种 bug 是不可以接受的。其中不乏 Elon Musk （Telsa/SpaceX）这种级别的用户。月活也是上亿的产品。 但是我迭代速度依旧很快，其实和现在 vibe coding 来说一样是 vibe coding，只是没有 AI 而已。 为什么他们放心让我来做呢？其实是他们没有选择，因为只有我一个人从读专科的时候就在写 React，写 Webpack，写 React Native，整个团队也只有我能解决这个问题，那我就很快的被升职了，就这么简单。不是因为 title 如何，也不是因为起点如何，也不是因为出身如何，是因为谁能解决问题。这就是为什么每天大家都在讨论 Wacoding，就是因为它能解决问题。 值钱的是问题，远不止是方法。 所以我觉得工程能力是道不是术，像 Cursor 的设计师也说到，就是周易里面这句话。@ryolu_：「形而上者謂之道，形而下者謂之器」 所以道很重要，高层级有点哲学向的方法论更重要，而不是说 vibe coding 与否，用 AI 不用 AI 与否，或者是 title 是不是 senior。

In 2014, JavaScript devs were struggling with bloated bundles. ES6 was the future, but most were still stuck with Babel and Browserify. 🧵

@_anniebabannie_ breaking out Browserify #epicwebconf

Browserifyプラグインの命名ルールが末尾に〜ifyをつけることだったのっていま思い出すとかわいい

Excuse me but I will not stand for this Browserify erasure. Browserify currently has 1.5 million downloads, almost 10X Parcel, and yet it's not listed? What gives. Are we letting these bundlers compete on an even playing field or not? npmjs.com/package/browserify

npm much worse Take a front-end language, make the whole thing backend, force front end people to use backend packages and browserify them to work on the front end, which there’s a great chance they will not Those who don’t write vanilla spend 97% of their time managing packages instead of building

Gulp, grunt, browserify, webpack