Community
Chat Logs
Sunday, May 31, 2026
- * phaleth joined #primate
- phalethnew-linker? naming is hard https://ziglang.org/devlog/2026/?2026-05-30#2026-05-30
- nevetDevlog ⚡ Zig Programming Language
- * phaleth joined #primate
- bluehi phaleth
- phalethhi blue
- bluewhat's up?
- phalethwatching go tutorial
- phalethcan you restart the VPS again?
- phalethit should start containers on boot now
- blueya
- * blue joined #primate
- bluemise ERROR Failed to install tools: aqua:npm/cli@latest, npm:pnpm@11
- bluemise is just pure and utter nuclear waste
- phalethyeah, stuff does not work
- blue[master 53c2aa52] merge i18n into general config, add i18n to marko 144 files changed, 1430 insertions(+), 944 deletions(-)
- bluegreat, more nonsense
- blueanyway, website is ported now, phaleth
- phalethoh, cool
- bluehttps://github.com/primate-run/primate/commit/09ffcfccc2ec0b16b39ce651c11f673880ab5984
- nevetwebsite: port to marko · primate-run/primate@09ffcfc
- bluebtw, let me show you what I meant earlier
- bluehttps://github.com/primate-run/primate/tree/master/packages/marko/src/private/tags
- bluesee those marko tags? they are uncompiled
- bluehttps://github.com/primate-run/primate/blob/master/packages/marko/package.json#L38-L39
- bluethis tells any loader/bundler to use the marko runtime condition with them
- bluehttps://github.com/primate-run/primate/blob/master/packages/marko/src/private/init.ts#L7
- bluethis tells the primate esbuild bundling process to associate any "marko" runtime key entries with this module (marko)
- blueso we're gonna publish .marko files to npm, and what I meant earlier with "leaf compilation" is that they're only going to be compiled to js during a primate app build
- bluethe most obvious benefit here is that I don't need to precompile them on an older version of marko that may be missing optimisations, and also I don't need to precompile them twice (once for server, once for client)
- blueI'm shoving the compilation dept to the end user, which is great
- bluedebt*
- phalethand if the project does not use fields or forms?
- bluethen the project doesn't import them and they're not in the bundle
- bluethis is the case for primate website
- phalethyay
- blueI kinda feel like making a version of it. I had other stuff planned but this has grown out of proportion
- blue"full marko 6 support" is good enough I think
- phalethyeah, cut the release if the deployment goes well
- blueso one thing I noticed is that the smallish icon next to the blog poster's name is slightly off. need to see what happened there, but otherwise sohuld be identical
- phalethI'm strugling with a bit of blur https://images4.imagebam.com/ee/15/cd/ME1DI7WG_o.png
- bluewoah, wth is THIS
- blueyou got hacked?
- phalethit was a linux update
- blueoof
- blueanyway, I'm gonna prepare the .39 release. I'll cut it once I have the go from you for the website
- phalethok, cool
- phalethI'm on it
- blue+1
- phalethnot sure what to do with this https://upaste.de/raw/7Xm
- bluehm
- bluefixing
- phalethlooks like dinit just has to be built from source
- blueoh
- bluephaleth: I pushed out a fix
- phalethok, cool
- blueI got the .39 blog post almost done, I think
- phaleth`npm start` works
- phaleththe docs page is all smashed together
- bluedid you compile packages?
- phalethyeah
- phalethhttps://images4.imagebam.com/33/ab/3c/ME1DIAMP_o.png
- phalethprod build is the same
- bluethat weird, looks good on brave
- bluewhat browser is that?
- phalethlibrewolf
- bluek, lemma install
- blueoof, 1.05G
- phalethsame on palemoon
- phalethdocs page looks good on epiphany
- phalethoh, actually the same problem is on epiphany too
- phalethyou can install epiphany using pacman
- phalethjust make sure the window is big enough
- phalethhttps://images4.imagebam.com/ed/c6/7a/ME1DIARE_o.png
- bluephaleth: fixed
- phalethdisplay: grid I think
- bluethe copy button doesn't work, I'm aware of that
- blueya
- phalethok, cool
- phalethcopy button does work for me
- blueon the blog?
- blueI get
- blueand import it in any view:
- blueugh
- blueapp.js:1633 Uncaught TypeError: Cannot read properties of undefined (reading 'writeText') at snippet.addEventListener.signal.signal (app.js:1633:31)
- bluesnippet.addEventListener.signal.signal @ app.js:1633
- phalethok, another one
- phalethgo to the guides page and then refresh, the text will get squashed
- phalethsimilar happens on blog page, but not so bad
- bluewhich browser? librewolf?
- phalethlibrewolf and palemoon
- phalethI'll try epiphany
- phalethyeah, squashed on epiphany as well after refresh
- bluewhy are you using these ridiculous browsers
- blueanyway, looking at it
- phalethfor testing mostly
- phalethactually librewolf is my main browser :)
- blueI went to the guides page on librewolf and refresh, nothing weird happened
- bluerefresehd*
- phalethok, let me try on primate.run then
- phalethworks well there
- bluedo you get any console error on refresh?
- phalethnope
- bluebtw, the copy bug was me running the website on 0.0.0.0
- bluechrome blocks certain APIs like navigator.writeText on that
- bluerunning from 127.0.0.1 worked
- blueso that's not a bug, ok
- phalethif I turn off display: grid rule on the guides page then it looks fine
- phalethdo you think the previous commit fixed docs but broke guides page? and also blogs page
- bluethe thing is, I didn't add display: grid
- phalethyeah, I have no problem copying text
- blueI just scoped one component which set `display: block` on main and caused havoc
- bluelet me install epiphany
- phalethepiphany is the best
- phalethheh
- phalethwait, you have edited guides view in that last commit
- blueyes
- blueI scoped it
- blueyeah, hitting f5 countless times on /guides does nothing wrong, on epiphany
- blueare you donig npx primate
- blueor npx primate build && npx primate build?
- bluewhen you're testing now
- blueI tested mostly with npx primate
- phalethnpm run build && npm run serve
- bluek
- phalethwill try npm start
- blueoh ok. yes if I refresh the guides page, it shows all black
- phalethwhen using npm start it's fine
- phalethso only the prod build messed up with styles
- blueyeah. so if you access /guides directly, it'll be messed up
- phalethright
- blueanywy I fixed it locally. will push in a moment. apparently the marko scoped styles are botched
- blueI don't really get it, it's related css modules, but it's also not important enough for me to care
- bluerelated to*
- phalethyeah, css does not need to be split too much
- blueanyway, pushed
- blueI also pushed out the blog post already because, why not
- bluerealy nice bundle size at 71K there
- bluereally*
- phalethok, take a note of https://pagespeed.web.dev/analysis/https-primate-run/2kwdd4vhoi?form_factor=mobile
- blueok, for comparison?
- phalethright
- phalethwell, new error
- blueoh no ;;
- phalethhttps://upaste.de/raw/aLV
- bluewait, Error.svelte?
- blueoh right
- phalethyeah, no clue
- blueit's in +error.ts
- bluecan you fix it locally?
- blueroutes/+error.ts
- bluejust change to .marko
- phalethmy IDE shows blur
- phalethbut I will try
- blueI can fix it for you if you wat
- phalethyeah, that'd be better
- bluedone
- phalethit needs to be commited anyway
- blueya
- phalethstill getting: ReferenceError: example is not defined
- phalethonly the docs page works now
- phaleththat commit with the blogpost broke the site
- blueit works locally, weird
- phaleththere are at least a couple of changes from <style/styles> to <styles> in marko components in that commit
- phalethcan you try to prod build?
- phaleththe dev build is also broken on frontpage and guides page
- phalethbut prod build is giving this error:
- phaleth[ERROR] views/Index.marko error: ReferenceError: example is not defined
- blueoh ok, I'm getting it as soon as I open a page
- bluegood
- bluepushed a fixed, phaleth
- bluefix, even
- phalethok, nice
- phalethone last thing, can you try prod build, visit the blog page and then refresh?
- bluepushed out another commit which fixes the icon distance on blog
- phalethok, then one sec
- bluethat probably fixed that, phaleth
- phalethyeah, that's fixed now, cool
- bluegood
- phalethalright, time to deploy
- bluegood
- phalethscore is better https://pagespeed.web.dev/analysis/https-primate-run/n0qol3q931?form_factor=mobile
- phalethgreat, there are no mentions of unused JS
- phalethmarko is very good it seems
- blueya
- phalethis it now on par with the other 5 frontend frameworks? from the point of view of primate
- blueyes
- bluehttps://primate.run/blog/primate-039#marko-6
- phalethoh, the post is up
- phalethnice
- blueyeah, gonna cut the release soon
- phalethI guess then docs are not fully up to date yet, such as this comparison table https://primate.run/docs/frontend#overview
- phalethabout 16kBs gzipped JS is gone, that's a huge drop
- bluewoah
- blueedited the table, will soon commit
- phalethok
- bluecommit is out
- blueI'm gonna prepare the release
- phalethre-deployed
- bluenice
- phalethlooks like svelte components can now use TS?
- blueyes
- bluethis has been the case since svelte 5
- blueI told you about it during our preprocess discussion
- blueso running test:apps now, and if all goes well, will cut the release
- phalethah, ok, was just wondering cause primate website was not using that
- bluetrue
- phalethbut I guess since svelte is gone who cares
- blue100%
- blueman those database tests are taking forever
- blueI need to setup ci
- blueI guess another bullet point for repopack
- blueanyway, this release unlocks two things that have blocked me, typed path parametrs in client (for repopack) and marko (for website optimisations)
- blueso I'm one happy puppy
- phalethI like crossbuilding, kinda odd for JS
- phalethbut that's where JS has gotten
- blueyup
- bluecould you redeploy please? or let me know how to easily redeploy, do we have a script or something?
- phalethsudo curl --silent --unix-socket /run/podman/podman.sock -X POST "http://d/v1.0/libpod/local/build?t=localhost/primate-site-runtime&localcontextdir=/opt/podman/primate-site/runtime&nocache=true"
- bluethat's all? cool
- phalethsudo podman stop 000000-primate-site-runtime-2 && sudo podman rm 000000-primate-site-runtime-2 && sudo podman run --detach --name=000000-primate-site-runtime-2 --runtime=runsc --network=000000-primate-site --ip=192.168.2.6 --publish=127.0.0.1:24431:6161 --cpus 1 --oom-score-adj -1000 --restart=always localhost/primate-site-runtime
- phaleththat's all
- bluecool
- bluenice, worked
- phalethgood
- blueok, all packages published
- phalethbig release
- blueyup
- phalethI should learn marko :D
- blueha
- bluephaleth: I completely forgot about entrypoints. lol
- blueI should add that to the blog post
- phalethoh, yeah, me too
- bluewelp, the 0.40 dev cycle is open
