Draft: Scratch changes for matrix-public-archive

[MadLittleMods]

Scratch changes for matrix-public-archive (not available yet)

See plan https://docs.google.com/document/d/1wP_TIqmBQjtt862vb2CWWmnmVxTyolcF3J1scuiYMdg/edit#

1. Trying to make it faster/easier to build hydrogen.es.js for local linking and dev in matrix-public-arhive project
   • yarn run vite build -c vite.sdk-lib-config.js --watch
2. Some random changes to accomodate using raw EventEntry's

Dev notes

• https://github.com/vector-im/hydrogen-web/blob/master/doc/SDK.md

Supporting the Node.js CommonJS environment (package.json exports)

Getting CommonJS vs EcmaScript Modules working, d7290bf
package.json

"main": "./hydrogen.cjs.js",
  "exports": {
      ".": {
          "import": "./lib-build/hydrogen.es.js",
          "require": "./lib-build/hydrogen.cjs.js"
      },
      "./paths/vite": "./paths/vite.js",
      "./style.css": "./style.css",
      "./assets/": "./asset-build/assets/"
  }

Also added "./assets/": "./asset-build/assets/" to the exports so we can simply serve them with app.use(express.static(path.dirname(require.resolve('hydrogen-view-sdk/assets/'))));

eslint-plugin-node will complain about these entries but that's because it doesn't support exports, see mysticatea/eslint-plugin-node#255

package.json exports docs

Docs source: https://github.com/webpack/webpack.js.org/blob/627c26026678f2f44c40a7631c7799c04936ff40/src/content/guides/package-exports.mdx (served at https://webpack.js.org/guides/package-exports/)

In general the exports field should contain an object
where each properties specifies a sub path of the module request.
For the examples above the following properties could be used:
"." for import "package" and "./sub/path" for import "package/sub/path".
Properties ending with a / will forward a request with this prefix to the old file system lookup algorithm.
For properties ending with *, * may take any value and any * in the property value is replaced with the taken value.

An example:

{
  "exports": {
    ".": "./main.js",
    "./sub/path": "./secondary.js",
    "./prefix/": "./directory/",
    "./prefix/deep/": "./other-directory/",
    "./other-prefix/*": "./yet-another/*/*.js"
  }
}

Vite

• Pre-Bundled dependencies used over locally linked dependency when built before linking vitejs/vite#6718

Server-side render Hydrogen

Can we just render straight to string?

 - There are lot of side-effects in the `render` functions of various components and calling `render(...)` will cause children to call `view` and `mount` which will do more DOM things.

Virtual DOM:

• https://github.com/jsdom/jsdom
• https://github.com/cheeriojs/cheerio

[MadLittleMods]

This makes emoji reactions show up on messages.

(the m.reaction events are in the list of events we're rendering)

[MadLittleMods]

Just trying to not render the composer when no vm.composerViewModel.kind matches with the goal to hide the composer.

[MadLittleMods]

Split off to #1100