Search
481 results for “develwithoutacause”
-
#HydroActive supports deferring upgrade / lifecycle hooks until the component is interacted with, solve load ordering so your dependencies are always upgraded, and manages dependencies on components so they are hydrated exactly when they need to be and no earlier.
-
#HydroActive supports deferring upgrade / lifecycle hooks until the component is interacted with, solve load ordering so your dependencies are always upgraded, and manages dependencies on components so they are hydrated exactly when they need to be and no earlier.
-
#rules_prerender tries to go a step further with partial prerendering at build time (reducing rendering work on the server) and driving *bundling* by what gets rendered, not just how resources are loaded on the client. We can eagerly load all required JS and CSS up front.
-
#rules_prerender tries to go a step further with partial prerendering at build time (reducing rendering work on the server) and driving *bundling* by what gets rendered, not just how resources are loaded on the client. We can eagerly load all required JS and CSS up front.
-
#rules_prerender tries to go a step further with partial prerendering at build time (reducing rendering work on the server) and driving *bundling* by what gets rendered, not just how resources are loaded on the client. We can eagerly load all required JS and CSS up front.
-
#rules_prerender tries to go a step further with partial prerendering at build time (reducing rendering work on the server) and driving *bundling* by what gets rendered, not just how resources are loaded on the client. We can eagerly load all required JS and CSS up front.
-
#rules_prerender tries to go a step further with partial prerendering at build time (reducing rendering work on the server) and driving *bundling* by what gets rendered, not just how resources are loaded on the client. We can eagerly load all required JS and CSS up front.
-
Cool to see #MDN exploring a unique #frontend architecture which better meets their needs.
https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/
A lot of the core ideas here are stuff I've been trying to formalize in #HydroActive and #rules_prerender. Islands of reactivity on a mostly static page and driving resource loading by what gets rendered are both key features most FE systems lack.
-
Cool to see #MDN exploring a unique #frontend architecture which better meets their needs.
https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/
A lot of the core ideas here are stuff I've been trying to formalize in #HydroActive and #rules_prerender. Islands of reactivity on a mostly static page and driving resource loading by what gets rendered are both key features most FE systems lack.
-
Cool to see #MDN exploring a unique #frontend architecture which better meets their needs.
https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/
A lot of the core ideas here are stuff I've been trying to formalize in #HydroActive and #rules_prerender. Islands of reactivity on a mostly static page and driving resource loading by what gets rendered are both key features most FE systems lack.
-
Cool to see #MDN exploring a unique #frontend architecture which better meets their needs.
https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/
A lot of the core ideas here are stuff I've been trying to formalize in #HydroActive and #rules_prerender. Islands of reactivity on a mostly static page and driving resource loading by what gets rendered are both key features most FE systems lack.
-
Cool to see #MDN exploring a unique #frontend architecture which better meets their needs.
https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/
A lot of the core ideas here are stuff I've been trying to formalize in #HydroActive and #rules_prerender. Islands of reactivity on a mostly static page and driving resource loading by what gets rendered are both key features most FE systems lack.
-
-
-
Exploring an #AI workflow for automatically fixing flaky tests, and having reasonable success with it.
https://github.com/angular/angular/pull/68026
#Bazel is actually a particularly nice fit with features like `--runs_per_test`. I expect any Bazel #web workspace could probably use this prompt mostly as-is.
-
RE: https://hostux.social/@defcon201/116324484796527679
Quick #story time: I was on a team which accidentally shipped sourcemaps to production!
The production server would serve sourcemaps for local dev, and we built sourcemaps in prod to deobfuscate errors but they weren't provided to the server in the prod environment.
You might see the hazard there. An innocuous change to our #Bazel build structure accidentally pulled in sourcemaps into the server, which it then helpfully served.
This was an app in the #Google monorepo too, so we were revealing all our source code as well as all our dependencies!
-
Free #startup #idea: A #GitHub bot which daily/weekly runs all the tests in your repo, looks for flakey targets, and then creates #AI generated fixes to improve stability.
#Nrwl #Nx self-healing CI is the closest existing example I can think of, but maybe there's something else out there I'm not aware of.
-
Free #startup #idea: A #GitHub bot which daily/weekly runs all the tests in your repo, looks for flakey targets, and then creates #AI generated fixes to improve stability.
#Nrwl #Nx self-healing CI is the closest existing example I can think of, but maybe there's something else out there I'm not aware of.
-
Free #startup #idea: A #GitHub bot which daily/weekly runs all the tests in your repo, looks for flakey targets, and then creates #AI generated fixes to improve stability.
#Nrwl #Nx self-healing CI is the closest existing example I can think of, but maybe there's something else out there I'm not aware of.
-
Free #startup #idea: A #GitHub bot which daily/weekly runs all the tests in your repo, looks for flakey targets, and then creates #AI generated fixes to improve stability.
#Nrwl #Nx self-healing CI is the closest existing example I can think of, but maybe there's something else out there I'm not aware of.
-
Free #startup #idea: A #GitHub bot which daily/weekly runs all the tests in your repo, looks for flakey targets, and then creates #AI generated fixes to improve stability.
#Nrwl #Nx self-healing CI is the closest existing example I can think of, but maybe there's something else out there I'm not aware of.
-
I remain convinced that the #Git CLI is a terrible UX and an especially bad fit for AI agents. Evidence:
```
GIT_SEQUENCE_EDITOR="python3 -c \"import sys; p=sys.argv[1]; c=open(p).read(); open(p,'w').write(c.replace('pick 29507ade4d6', 'edit 29507ade4d6'))\"" \
git rebase -i 29507ade4d6^
```I only asked it to take some local changes, break them up, and amend them to some existing individual commits and it is thrashing *wildly* but I'm scared to abort or it'll leave me in a potentially worse state.
I'm been playing with #Jiujitsu on the side, I wonder if that might work better?