ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. bluehi phaleth
  2. phalethhi blue
  3. liolocHey guys
  4. phalethhi lioloc
  5. bluehi lioloc
  6. dreamrealnew BCN piece, in which I FINALLY show some disdain for that moron Joe Biden
  7. dreamrealand, for that matter, Satya Nadella
  8. bot[ByteCode.News] Learn to Imagine - https://bytecode.news/posts/2026/10/learn-to-imagine
  9. bluenice!
  10. bluedreamreal: who is Staya Nadella? sounds like an indian scammer
  11. * blue reads the article
  12. phalethM$'s CEO
  13. dreamrealSatya Nadella is MS' CEO.
  14. dreamrealYou need a heavy dose of curiosity, my friend. :D
  15. dreamreal"BILL Gates? BILL? What kind of dumb name is that for a professional? Sounds like a loser." (meanwhile William Gates buys the country the speaker lives in using pocket change.)
  16. bluedreamreal: I'm very rarely interested in people. and the more I know of the world, the less I like (-Elizabeth Bennet, Pride & Prejudice)
  17. dreamrealYet Ms. Bennet, while a dcent character in a well-known novel, is doing a poor job of actually humaning
  18. blueshe's great, you big oaf
  19. dreamrealShe also spends the rest of the novel finding out she was incorrect about people
  20. bluepresumptive, not incorrect!
  21. dreamrealso she becomes great as she abandons the POV you just mentioned :D
  22. dreamrealAnyway, satya might indeed be a scammer, he's certainly indian, but he's hardly the kind of indian scammer you're thinking of, and he's not exactly unknown
  23. blueincidentally, as I've told you before, all the indians I know are scammers, which doesn't help his case
  24. dreamrealYou need to meet more people.
  25. blueso that I like the world even less?
  26. dreamrealblue: no, so you can learn to humanize the people you make assumptions about
  27. dreamrealI know a lot of indians, I know a lot of indians I do not like, and I have good reasons for that, but EVEN SO when I meet a new indian I evaluate them for who they are and not based on what characteristics I know about
  28. blueI don't need to humanise anyone, they're already humans. they either disappoint me or I approve of them
  29. blueand they mostly disappoint me
  30. bluephaleth: clankers really love wasting time on nonsense
  31. blueI just had a clanker who overread a linting rule and decided he now needs to start fixing the entire world
  32. phalethyeah, I can tell they like to waste time
  33. phaleththere is a lot of cruft in the repopack project, I've done some minor cleanup you should merge
  34. phalethand clanker should not get involved
  35. blueya
  36. blue773 is merged
  37. phalethcool
  38. bluephaleth: https://repopack.com/project/flog/tasks/123
  39. bluecan you try again once flog builds
  40. phalethyeah
  41. phaleththat fixes the problem
  42. bluenice
  43. bot[Node.js Blog] Node.js 26.13.0 (LTS) - https://nodejs.org/en/blog/release/v26.13.0
  44. dreamrealblue: what's the path for using flog for the ui-primate build in streampack?
  45. bluedreamreal: I think phaleth charted it already. generally speaking: 1) install flog, 2) remove package-lock.json, 3) run `flog lock` 4) potentially clean up the overrides you have in package.json, I don't think you need them
  46. bluein particular, I don't think
  47. blue "overrides": {
  48. blue "fflate": "0.7.5"
  49. blue }
  50. blueachieves much
  51. dreamrealWould we need to alter the dockerfile any?
  52. phalethit's not that easy there is some extra registry defined .npmrc and I don't know if the project uses that
  53. blueare you running your own npm reigstry?
  54. bluedreamreal: ^
  55. dreamrealyes, I have my own nexus
  56. phalethanyway, if you wanna try make sure flog.lock is generated as explained here: https://flog.run/docs/install#portable-target-locks
  57. nevetDependency installation · flog
  58. bluelet me see if flog supports that
  59. dreamrealThat would mostly impact publication, will have to see
  60. bluedreamreal: sorry, I posted in another channel
  61. dreamrealI saw :D
  62. dreamrealthe three channels are all in the same window in weechat for me :D
  63. blueoh ok
  64. blueanyway, for phaleth's information, clanker said .npmrc should be supported
  65. phalethwell, I was able to build the frontend the other day
  66. phalethusing flog
  67. dreamrealOKAY! installation for flog is broken on mac:
  68. dreamrealsh: line 964: Support/flog/config.toml: No such file or directory
  69. bluelet me see
  70. blueworkaround for now: curl -fsSL https://flog.run/install | FLOG_CONFIG="$HOME/Library/Application Support/flog/config.toml" sh
  71. blueI will fix the installer for mac
  72. dreamrealokay, flog lock worked well enough, flog install, flog run build?
  73. phalethRUN flog install
  74. phalethRUN flog build
  75. dreamrealWell, the current dockerfile uses npx from node:26-alpine, so I'd need to install flog, and change that npx primate build to flog run build, yes?
  76. phalethdreamreal: https://upaste.de/raw/EVv
  77. phalethin short there is no flog docker image
  78. dreamrealI know.
  79. dreamrealflog.lock looks like it's bound to the instance on which it's run - so I'd be stuck running flog lock in the docker image itself, yeah?
  80. dreamrealOr am I misunderstanding?
  81. phalethnope, pre-generate flog.lock as described here https://flog.run/docs/install#portable-target-locks
  82. nevetDependency installation · flog
  83. bluedreamreal: mac installer is fixed
  84. bluedreamreal: flog.lock is to flog, what package-lock.json is to npm
  85. blueyou generate it once, commit it, and in the case of your dockerfile, copy it
  86. dreamrealYep, I'm just working out the requirements, since I'm guessing some, learning as I go
  87. * blue is back to reading Crafting Interpreters
  88. bot[Node.js Blog] Node.js 24.22.2 (LTS) - https://nodejs.org/en/blog/release/v24.22.2
  89. dreamrealblue: satori is asking for 0.7.3 for fflate and seems to show 0.7.3 in use?
  90. dreamrealblue: how can I help
  91. bluedreamreal: help with that? 0.7.3 is the latest in 0.7.*
  92. dreamrealthe override should apply, no?
  93. blueit won't, but you also don't need it. 0.7.3 is the latest on npm. just add fflate as a normal dep `flog add fflate@^0.7.3`
  94. bluesatori has this: "fflate": "0.7.3",
  95. bluefor some reason it's pinned. I don't know why, but you can do the same. or just leave it out since it's a transitive dep
  96. bluelike, I don't know why you need that override at all
  97. dreamrealOkay, this is an audit thing
  98. dreamrealhttps://registry.npmjs.org/fflate/-/fflate-0.7.5.tgz exists, it's suggested by audit, satori asks for 0.7.3 specifically
  99. dreamrealflog is nesting 0.7.3 under satori (node_modules/satori/node_modules/fflate)
  100. dreamrealand that release is flagged - it might not be being CALLED in an unsafe manner, it may not matter at all