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.
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.
Of course I could try targeting Node.js - a topic for another day.
April 29, 2025 at 11:44 PM
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.
Of course I could try targeting Node.js - a topic for another day.
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 🧐 ?
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...
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...
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...
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.
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
For many of us Devs, making an API call and doing sth with the response is “the start of the visible job”, but it’s worthy to take 5’ once in a while to appreciate and admire the hard work put into the submerged parts of the iceberg, one of which is TLS.
December 26, 2024 at 3:00 PM
For many of us Devs, making an API call and doing sth with the response is “the start of the visible job”, but it’s worthy to take 5’ once in a while to appreciate and admire the hard work put into the submerged parts of the iceberg, one of which is TLS.
just learned today that I need both lines in my Workspace settings to have `deno fmt` as the default formatter for .ts files.
It's cuz VS Code has its own "TypeScript Format" User setting, which somehow overwrites Workspace setting. I have non-Deno ts projects too, so this is the best of 2 worlds.
It's cuz VS Code has its own "TypeScript Format" User setting, which somehow overwrites Workspace setting. I have non-Deno ts projects too, so this is the best of 2 worlds.
December 15, 2024 at 4:16 PM
just learned today that I need both lines in my Workspace settings to have `deno fmt` as the default formatter for .ts files.
It's cuz VS Code has its own "TypeScript Format" User setting, which somehow overwrites Workspace setting. I have non-Deno ts projects too, so this is the best of 2 worlds.
It's cuz VS Code has its own "TypeScript Format" User setting, which somehow overwrites Workspace setting. I have non-Deno ts projects too, so this is the best of 2 worlds.
TS helps me deal with things I can never (or don’t want to) remember myself, eg Open API schema declaration (illustration img below).
Such a pity that many folks are (ab)using TS towards the direction where it causes pains and frictions more than it helps. Good intention, poor practicing.
Such a pity that many folks are (ab)using TS towards the direction where it causes pains and frictions more than it helps. Good intention, poor practicing.
December 8, 2024 at 3:44 AM
TS helps me deal with things I can never (or don’t want to) remember myself, eg Open API schema declaration (illustration img below).
Such a pity that many folks are (ab)using TS towards the direction where it causes pains and frictions more than it helps. Good intention, poor practicing.
Such a pity that many folks are (ab)using TS towards the direction where it causes pains and frictions more than it helps. Good intention, poor practicing.
When our REST API Schema and implementation logic live in the same code space, parameter parsing and Open API doc generation happen together... Efficient. Centralized. Let alone Elegant.
Demo code: replit.com/@sephdinh/au...
#oak, #oak-routing-ctrl
Demo code: replit.com/@sephdinh/au...
#oak, #oak-routing-ctrl
December 5, 2024 at 6:35 PM
When our REST API Schema and implementation logic live in the same code space, parameter parsing and Open API doc generation happen together... Efficient. Centralized. Let alone Elegant.
Demo code: replit.com/@sephdinh/au...
#oak, #oak-routing-ctrl
Demo code: replit.com/@sephdinh/au...
#oak, #oak-routing-ctrl