iiinova — where your digital self keeps evolving

dk @mrkha.ng · 01/05/2025

I’ve also run into several ppl with a very strong opinion against “javascript on the server”. I’m pretty sure there are countless horrors about bad JS on the server, but isn’t it like saying all ppl shouldn’t live on Earth cuz there are bad ppl 🤔 anyway each to their own, as i often tell myself 🤷

010

dk @mrkha.ng · 30/04/2025

honestly, I never ever, ever thought fullsoak.dev would work with Shadcn one day. Disclaimer: at the current state, it's obviously alpha work & heavily discouraged on PROD or anything serious, actually. I just find it hard to believe myself that it does somehow work. Will link to source code later.

020

dk @mrkha.ng · 30/04/2025

NB: when everything works, this is what we're supposed to have (the code & the output)

fullsoak demo, the react component example code

fullsoak demo, the final visual output (server-side rendered HTML)

fullsoak demo, the final output source code (server-side rendered HTML)

000

dk @mrkha.ng · 30/04/2025

PS: I also tried the sass-embedded non-async API, which is `compile` (instead of `compileAsync`) and bumped into another brick wall. Here a dependency `sync-message-port` doesn't seem to be fully compatible with Deno. Of course I could try targeting Node.js - a topic for another day.

100

dk @mrkha.ng · 30/04/2025

I hacked my way pretty deep into forcing a non-conventional use of the sass-embedded library. At this point, deploying to a standard VPS seems like the only viable choice, as Deno Deploy doesn't allow subprocess, which is needed by sass-embedded. Tho, is there any other route for FullSoak.dev 🧐 ?

100

dk @mrkha.ng · 08/04/2025

Totally find to have a healthy mix of non-programming topics. Makes us, uhm, less LLM like 😆

110

dk @mrkha.ng · 31/03/2025

E.g: git-ssh clone, or a certbot follow-up work which talks to supporters.eff.org:443 - they all fail. Not sure if it's because I missed some additional setups, or just a coincident. But it'd be funny if it's 2025 and not all processes and machines do IPv6 OOTB 🤔

000

dk @mrkha.ng · 31/03/2025

I recently enabled IPv6 only for my AWS EC2 instance. Stressed on IPv6 _only_ ie. the server has zero IPv4 interface. I notice: while most tasks still happen normally, some outbound requests (esp. ssl) fail consistently.

110

Reposted by dk

Adam Argyle @nerdy.dev · 20/03/2025

#CSS only carousels arrive in Chrome 135 ⤷ nerdy.dev/css-carousel...

1322340

dk @mrkha.ng · 21/03/2025

As someone who recently had to Box<dyn std::err::Error> all the things (also i try to cut down on external libs like anyhow), i find this post very educational. Thank you :)

010

dk @mrkha.ng · 11/03/2025

for example: this code works perfectly with the current tsc: github.com/fullsoak/ful... on both Deno Deploy and Cloudflare Workers I'm quite positive it'll throw like in the screenshots above the very moment the new TSC comes into play.

github.com

010

dk @mrkha.ng · 11/03/2025

ppl go crazy 'bout TSC going Go. Yes it's amazing, but doesn't mean JS-based compilers have no use anymore. for use cases where native bindings are `import`ed during runtime, unless it's direct VPS / inside Docker, it's a no-go for most hosting svc with a "sandboxed runtime" eg Cloudflare Workers

110

dk @mrkha.ng · 10/03/2025

"vibe-enjoying" an example SSR web page on such a #nobuild fullstack TypeScript framework. Feels like an escape to a breezy country life of simplistic values of basic web development, away from the sexy but stressful metropolitan life of layers of build configurations stacked on top one another...

010

dk @mrkha.ng · 05/03/2025

I take "barrier of entry" very seriously. A getting-start / demo codebase for a basic UI having more than a few lines of code, can already be a "conversion rate killer". but I myself am susceptible to this. Ytd I happened to push a commit that brought more lines than needed. reverted now. #kiss

simplifying code example to the bare minimum

000

dk @mrkha.ng · 05/03/2025

left: officially documented directory setup right: rebellious teenager FullSoak framework doesn't care. It just serves both. source code for the left: github.com/fullsoak/den... source code for the right: github.com/Thesephi/ful... *disclaimer: unofficial setup is only supported at best effort

000

dk @mrkha.ng · 04/03/2025

and that's how I have a huge crush on Zed's pride versioning standard 😂

000

dk @mrkha.ng · 04/03/2025

feeling a similar thing to the bone, too, as I'm hacking on a web framework. From the beach of SSR to the valley of JSX transpilation, then top the hill of posix vs windows vs Cloudflare filesystems (or lack thereof). just as one stops to take a sip, the shadow of (s)css mountain casts over...

110

dk @mrkha.ng · 03/03/2025

I want to provide out-of-the-box support for react-helmet (or preact-helmet actually). I'm short on time, yet it looks bad if there's zero support for basic title & meta tags, so a bespoke API: makeHat why Hat? cuz it's like a Helmet, but way, way lighter (silly lol) usage: jsr.io/@fullsoak/fu...

000

dk @mrkha.ng · 27/02/2025

I got a micro EC2 instance back in 2007 or so. Today I wanted to switch it to nano. Did some googling. Followed the steps: - stop the instance - change instance type - start it again Boom, cannot start cuz ENA not compatible I switch instance type back It still.. doesn't start I'm now a 'happy' user

000

dk @mrkha.ng · 26/02/2025

Just randomly learned that the awesome people at @jsr.io got us this amazing dependency graph for our modules. We still have nice things in 2025, everybody!! 😆 (screenshot from jsr.io/@fullsoak/fu...)

031

dk @mrkha.ng · 24/02/2025

just released a bit more verbose example, with simple authentication, showing how a typical Web App can be built with the FullSoak framework Live Demo: fullsoak-guestbook.deno.dev Will be adding more features & colors down the road. Now I need some sleep 😅

100

dk @mrkha.ng · 23/02/2025

deploying a #FullSoak app cannot be simpler with #Deno #Deploy: - just leave all install / build options empty - declare the single entrypoint of our app (eg `src/main.ts`) and boom, the app is ready. see it for yourselves: fullsoak-examples.deno.dev/app source code: github.com/fullsoak/den...

000

dk @mrkha.ng · 18/02/2025

Now that the framework has taken some shape, I'll migrate the #buildinpublic log from this bsky account to a Discord server where 1) there are more rooms and 2) less spammy for you all here 😀 Here goes: discord.gg/hzGsVVKy2N I'll continue using this bsky account for "normal" posts. See you around!

discord.gg

Join the FullSoak Discord Server!

Community Support forum for FullSoak SSR Web Framework | 1 members

000

dk @mrkha.ng · 16/02/2025

Just added (experimental) support for Cloudflare Workers to FullSoak web framework Still rooms for perfection, but very happy to share a milestone. Lessons learned are noted in the demo code: github.com/fullsoak/clo... Live Deployment: fullsoak-cloudflare-workers-examples.dklab.workers.dev

000

dk @mrkha.ng · 16/02/2025

Finally decided on a fallback for SWC on Deno Deploy: `tsc` itself (surprised surprised 😅). Trade-offs are acceptable. For the 1st time since the initial PoC, this framework supports deploying straight into #DenoDeploy Live Demo: fullsoak-examples.deno.dev/app Details: github.com/fullsoak/ful...

log from Deno Deploy for the web page https://fullsoak-examples.deno.dev

000

dk @mrkha.ng · 15/02/2025

I should have known better. Both SWC and esbuild make use of native binding, which is apparently not yet supported by Deno Deploy. I left the discovery notes here: github.com/denoland/dep... Next explorative direction: maybe try something without native binding.

000

dk @mrkha.ng · 14/02/2025

On 2nd thought, I think I'll go with esbuild's jsx transform: esbuild.github.io/api/#jsx as it's still actively maintained. Whether SWC or esbuild, I'd love to conform to the 'no config' wish (ie: using 'best defaults'). If/when the community needs arise, we'll think about customization options.

esbuild.github.io

esbuild - API

100

dk @mrkha.ng · 14/02/2025

I already like Bublé by reading the first few intro lines: its focal points match those of FullSoak: - zero config - code is only altered where necessary Still, it's not without its limitations, eg. it doesn't support 'for...of' loops (1 thing I personally like). Maybe there're alternatives still?

110

dk @mrkha.ng · 14/02/2025

@swc/core has been used behind the scene by FullSoak to transpile JSX. It works seamlessly for Deno and Bun, but when using with Deno Deploy or Cloudflare Workers, the native binding doesn't work: github.com/denoland/dep... Thus im exploring buble.surge.sh/guide/ as a potential fallback.

buble.surge.sh

Bublé

The blazing fast, batteries-included ES2015 compiler

110

dk @mrkha.ng · 13/02/2025

Yup. It’s best for any 1-way communication need from server to client. For 2-way comm needs (ie chat apps), websocket is still a good standard though, so the article title is a tad too extreme 😅

110

dk @mrkha.ng · 12/02/2025

thanks @glitch.com for the kind words ☺️ It's a side project to self-challenge how far we can keep it "stupid simple" before business / technical requirements force it to bloat up in config & setups :) By the way, I tried deploying it on Deno Deploy but failed ironically 😂 github.com/denoland/dep...

github.com

[Bug]: The deployment failed: UNCAUGHT_EXCEPTION - Failed to load native binding for @swc/core · Issue #802 · denoland/deploy_feedback

Problem description I have a custom Deno project, in which I use @swc/core. It works on local & remote (Ubuntu 24.04.1 where I deploy manually myself). But when deploying with Deno Deploy, the step...

000

dk @mrkha.ng · 09/02/2025

idk how later gens look at LinkedIn, for gen Y & back who joined LinkedIn 15+ yrs ago, it was probably a place for mass connections with strangers in hope of (better) jobs. A Tinder for careers so to say. also these days we gotta pay to send msg unless we connect first. Free features win i guess?

000

dk @mrkha.ng · 06/02/2025

😂😂😂 I first read it as Challenge Accepted. Thanks for pointing it out. Guess we’re both challenged mhhh 🧐

000

dk @mrkha.ng · 06/02/2025

Thank you for the kind words ☺️ I’d love to use it on real projects and then let’s see how far we can reach before we can’t keep it barebone simple anymore 😅

110

dk @mrkha.ng · 05/02/2025

here's the source code for the example app in the footage above: github.com/fullsoak/exa... while this is a lab project, i hope we can strive to aim for production, scalable qualities during future development of this framework. Happy to discuss future directions! #deno #ssr #nobuild #webframework

github.com

examples/src at main · fullsoak/examples

examples using the FullSoak web framework. Contribute to fullsoak/examples development by creating an account on GitHub.

001

dk @mrkha.ng · 05/02/2025

Finally the 1st PoC is out of the oven: FullSoak - a Fullstack TypeScript SSR-first web framework. The design decisions shared so far are summarized in the README: jsr.io/@fullsoak/fu... Once again: I did this mostly as a self-challenge, to see how far we can keep-it-stupid-simple.

281

dk @mrkha.ng · 20/01/2025

That’s a nice pointer, thank you very much! Will defly help get some inspirations towards what can be applied to this project.

010

dk @mrkha.ng · 20/01/2025

The framework users can make decisions about which CSS rules to put in CSS files, and which to pass directly into the Preact components (ie. as one of the methods to avoid FOUC). Atm I'm not sure what the consequence of this decision will be. Any insight is much appreciated 🙏

110

dk @mrkha.ng · 19/01/2025

Design decision: I adore the straightforwardness of website development in the early 2000s. One html file linking to css files. Since this framework is SSR-first, I’d love to keep this stupidly simple mantra. I’ll think about scss at some point (for now it can be a separate, bring-ur-own thing).

110

dk @mrkha.ng · 19/01/2025

Design decision: While Preact endorses HTM (Hyperscript Tagged Markup), I wish to support both HTM and "traditional" JSX. Note: I do like HTM, but I'd assume the community is already very familiar with JSX. So even if I use HTM for myself, I wouldn't strip JSX support away from this framework.

000

dk @mrkha.ng · 18/01/2025

Design tradeoffs: My goal is SSR-first. I think it'll be crazy hard to design an SSR-first framework that also supports CSR & client-side routing seamlessly. Next.js and Remix may excel there. I won't have the resources to keep up. I'll treat those as "best efforts" and focus on SSR only for now.

000

dk @mrkha.ng · 18/01/2025

DX: Browserify, webpack, babel, all sorts of loaders & plugins: they helped me tremendously in the past. Still, I'm gonna ditch them all in this project. KISS attempt. Util functions (ie getServerSideProps, loader, handle etc.) are magical. I appreciate magic, but my memory is too weak for spells.

100

dk @mrkha.ng · 18/01/2025

PS on "KISS": when I say KISS I mean for the devs who work with the framework. I don't mean necessarily for the actual source code of the framework. I trust: the more simple a (working) piece of software seems from the outside, the more complex it is inside.

000

dk @mrkha.ng · 18/01/2025

Day 0: based tech selection --- DOM rendering: I've been a React user since ~2014 I picked up #deno in 2024 Deno Fresh endorses #preact So will I --- URL routing: I used Express, Koa I made github.com/somnusjs/som... based on Restify I made github.com/Thesephi/oak... based on Oak which I'll use

100

dk @mrkha.ng · 18/01/2025

Few notes on the intents behind: 1. I prefer to KISS; existing options are awesome, but a bit more bulky than my brain can handle (& I trust there are others like me) 2. I'd love to benchmark "how complex things need to be" to support standard business use cases. Let's see how long we can KISS.

100

dk @mrkha.ng · 18/01/2025

I'll start using this bsky account as an informal #buildinpublic diary of my progress designing a Fullstack TypeScript SSR web framework. It'll be quite opinionated, but not as "magical" as Next.js or Remix. OSS ofc. Not guaranteed to be better than existing options, but will be different for sure.

140

dk @mrkha.ng · 11/01/2025

for the RPG-gamer -turned #deno devs out there, remember NieR: Automata, because we'll constantly do: ``` deno test -NIER ``` ジ

000

dk @mrkha.ng · 06/01/2025

that's good to know! I maintain a small JSR library within the oak ecosystem 😉. And I've also been using codecov for only coverage thus far. Can't wait to check this out, thanks for the info! :)

000