dk
@mrkha.ng
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.
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.
April 30, 2025 at 2:22 AM
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.
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.
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 🧐 ?
Tho, is there any other route for FullSoak.dev 🧐 ?
April 29, 2025 at 11:34 PM
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 🧐 ?
Tho, is there any other route for FullSoak.dev 🧐 ?
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.
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.
March 31, 2025 at 4:35 PM
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.
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.
Reposted by dk
March 20, 2025 at 4:40 PM
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
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
March 11, 2025 at 11:08 PM
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
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
"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...
March 10, 2025 at 10:42 PM
"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...
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
but I myself am susceptible to this. Ytd I happened to push a commit that brought more lines than needed.
reverted now.
#kiss
March 5, 2025 at 11:52 AM
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
but I myself am susceptible to this. Ytd I happened to push a commit that brought more lines than needed.
reverted now.
#kiss
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
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
March 5, 2025 at 3:46 AM
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
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
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...
why Hat? cuz it's like a Helmet, but way, way lighter
(silly lol)
usage: jsr.io/@fullsoak/fu...
March 3, 2025 at 9:57 PM
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...
why Hat? cuz it's like a Helmet, but way, way lighter
(silly lol)
usage: jsr.io/@fullsoak/fu...
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
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
February 27, 2025 at 11:15 PM
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
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
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...)
(screenshot from jsr.io/@fullsoak/fu...)
February 26, 2025 at 12:22 AM
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...)
(screenshot from jsr.io/@fullsoak/fu...)
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 😅
Live Demo: fullsoak-guestbook.deno.dev
Will be adding more features & colors down the road. Now I need some sleep 😅
February 24, 2025 at 4:36 AM
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 😅
Live Demo: fullsoak-guestbook.deno.dev
Will be adding more features & colors down the road. Now I need some sleep 😅
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...
- 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...
February 23, 2025 at 6:27 PM
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...
- 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...
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!
I'll continue using this bsky account for "normal" posts. See you around!
February 18, 2025 at 12:50 AM
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!
I'll continue using this bsky account for "normal" posts. See you around!
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
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
February 16, 2025 at 10:25 PM
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
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
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...
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...
February 16, 2025 at 2:01 AM
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...
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...
@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.
Thus im exploring buble.surge.sh/guide/ as a potential fallback.
Bublé
The blazing fast, batteries-included ES2015 compiler
buble.surge.sh
February 14, 2025 at 8:29 PM
@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.
Thus im exploring buble.surge.sh/guide/ as a potential fallback.
Adapted the framework so it's compatible with Bun runtime as well. Example for Bun: github.com/fullsoak/bun...
February 10, 2025 at 1:50 AM
Adapted the framework so it's compatible with Bun runtime as well. Example for Bun: github.com/fullsoak/bun...
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.
Once again: I did this mostly as a self-challenge, to see how far we can keep-it-stupid-simple.
February 5, 2025 at 9:40 PM
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.
Once again: I did this mostly as a self-challenge, to see how far we can keep-it-stupid-simple.
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).
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).
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
---
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
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.
January 19, 2025 at 11:48 AM
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).
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).
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.
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.
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
---
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
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.
January 19, 2025 at 1:28 AM
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.
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.
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
---
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
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.
January 18, 2025 at 10:56 PM
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
---
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
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.
January 18, 2025 at 10:34 PM
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.
Ending 2024 with a library version bump, not sure if I should be happy or sad about it. But what’s done is done, here to hoping i’ll up my Rust skills a bit more in 2025 🦀🍾🎊
#rust #sdk #happynewyear
#rust #sdk #happynewyear
December 31, 2024 at 10:05 PM
Ending 2024 with a library version bump, not sure if I should be happy or sad about it. But what’s done is done, here to hoping i’ll up my Rust skills a bit more in 2025 🦀🍾🎊
#rust #sdk #happynewyear
#rust #sdk #happynewyear