⚡️ Move the web forward.
- Tweets 1,051
- Following 217
- Followers 4,837
- Likes 1,253
Say WHAAAAAAT??? 🤩
Do you want to see @pika/pack integrated directly into npm v8? Check this new RFC by the npm team 👀
2
12
41
.@stramel89 is being wayyyyyy too modest here, he's been actively involved with GitHub issues and providing pre-release feedback since the very beginning. Thank YOU for all your help, Michael. 😁
Google knows me too well. This popped into my feed today 😏 Awesome work by @FredKSchott and team! @pikapkg
1
2
12
👏👏👏
React Async is now using @pikapkg Pack to ship optimized bundles for each platform. v5 also adds support for the `promise` prop. react-async.dev #reactjs
1
Any TypeScript (@typescriptlang) experts able to help us come up with a solution to bring .d.ts support to @pika/web? It's possible today, but we want it to be painless & automatic.
Issue here ▶️ github.com/pikapkg/web/issue…
6
10
🔥 Hot off the presses, @pika/web v0.3.0 has been released with new CLI options, including: A new `--optimize` flag for serving dependencies in production!
6
13
Also curious: What % of devs would consider DX (@pika/web) > UX (an x% faster site) even for production?
(As a @pika/web benefit, this one would be contentious... 👹)
2
3
So, assuming all of the above is true, I'd wonder...
- @pika/web for dev, Webpack/Rollup/Parcel for production?
- @pika/web for new projects, bundlers to optimize existing?
- @pika/web for deps, bundlers for app src/ only? (could then guarantee import map depth of 2-3 levels)
2
3
5. @pika/web was a single command, no config, installed and ran without issues.
vs.
- Bundler A wouldn't install at all
- Bundler B installed, but needed to be configured
- Bundler B had so many options, hard to learn
- Bundler B built chunks to the wrong location, wouldn't load
1
1
1. Served statically, a @pika/web installation vs. an entire app bundled with Bundler X perform equally well on a flat import tree (1 index.js, 10 imports).
1
1
3
PS: all of this assumes HTTP/2 support. More info here: developers.google.com/web/fu…
1
1
Alright, I need to step away in a little bit. Not yet at a point where one could confidently conclude anything, but if I had to take a stab at it the rough data is looking like...
1
1
For anyone following along at home, I never found a fix for #2 either (I only spent a few minutes looking, and then decided to just add `mv dist/*chunk* .` after ever bundle call to unblock myself).
1
2
I'm also keeping a list of unexpected issues as I go. So far:
1. Node compilation failing when installing Bundler A, spent ~15 minutes Googling but couldn't solve.
2. Currently: Bundler B is importing chunks (that it created) from the wrong location 🤷♂️
1
1
Okay, making good progress on a new project. Here's the random assortment of 10 dependencies I'm starting with, based on a quick browse down pikapkg.com's popular list:
1
3
Hmm, these different projects are in different state of upkeep. Getting lots of warnings on several different installs... this may not be as easy as I thought.
May switch tactics and start with a contrived example and then come back to these at the end if I still have time.
1
2
Each of these has between 3-13 different web app dependencies, which should serve as a good survey.
1
2
Here's my starting list:
1️⃣ @ezekielchentnik github.com/ezekielchentnik/p…
2️⃣ @_developit github.com/developit/preact-…
3️⃣ @_developit github.com/developit/preact-…
4️⃣ @kristoferbaxter github.com/kristoferbaxter/p…
5️⃣ @lukeed05 github.com/lukeed/colors-app…
6️⃣ @IBMDeveloper's github.com/ibm-watson-data-l…
2
9