Chat Logs

  1. * jreicher joined #primate
  2. * phaleth joined #primate
  3. bluephaleth: hi
  4. phalethhi blue
  5. blue@primate/marko is going to experiment with publishing source files to npm; particularly .marko tags. I'm pushing for edge compilation
  6. phalethedge compilation?
  7. blueyes, the app itself should be the one compiling
  8. bluethe traditional npm trade is to precompile and then serve something like a dist.js or so
  9. bluethat is in some ways good and in many ways terrible
  10. phaleththe compiler is gonna be sent to the client?
  11. blues/npm trade/npm way/
  12. blueno
  13. phalethor as a dev tooling?
  14. bluewe're gonna publish source files, and the one compiling them is the app (in this case primate)
  15. phalethok, so devDependency then
  16. bluethat is because the app knows best what it needs, and what are the conditions for compiling the source files
  17. blueit's not directly related to devDependency
  18. blueit's just the question whether you precompile non-js or not
  19. blueif you precompile, you're more inclusive in who can consume it
  20. bluebut the truth of the matter is that you're only ever going to consume .marko files if you use marko, or .svelte files if you use svelte
  21. blueyou're not going to have a general-purpose, non-svelte apps that consumes a .svelte file
  22. blueapp*
  23. phalethwell, if it's some kind of optimizing compiler then I guess that's fine, but a lot of them are not
  24. blueso alongside @primate/marko, I'm providing two tags: <Field> and <Form>
  25. bluethe question is whether I precompile them or not
  26. blueI decided to not precompile them
  27. blueand just publish them directly to npm
  28. phalethnpm is full of broken stuff
  29. phalethI mean non-js
  30. blueyes, and I'm adding more broken stuff
  31. bluebut precompilation in the case of npm is the devil's work
  32. phalethat least you name it .marko and not .js
  33. blueyes, the svelte guys keep doing that and it drives me inside
  34. blues/inside/insane/
  35. bluethere's more beauty to it, though: I'm using the `marko` runtime key to drive that compilation
  36. bluethis is arguably one of the best use cases of runtime keys
  37. bluehttps://github.com/primate-run/primate/commit/b0eb1187313cdd49946c5b46d7bbef8df688e004
  38. nevetmarko: full support for version 6 · primate-run/primate@b0eb118
  39. blueyou can see the work here. it doesn't include the .marko runtime key yet though
  40. bluenote that unlike all the other frontends we support, marko does not have a meta framework for it, so primate's gonna be the first (that I know of, anyway)
  41. phalethif marko can replace svelte on primate website while not adding more bloat then lets use marko
  42. bluethat's the idea, and it might work for 0.38
  43. blue0.39*
  44. * jreicher joined #primate