Notices by zac anger (zacanger@mastodon.social), page 15

moved teams again today. maybe I'll stay with this one for a few months.

published a new module: http://npm.im/path-normalize. It's not the same as normalize-path -- normalize-path only handles slashes, my module is pretty much an exact copy of Node's posix path.normalize that happens to work in the browser.

hey mastodon
https://twitter.com/loonasbian/status/967604951353577472

potentially controversial opinion: Pieces of You was the best album of the 90s

i forgot about this until today
https://www.youtube.com/watch?v=O_ZUmMzP5ts

so here's a thing https://youtu.be/Vd9Z1JN2Xjw

i'm also uploading a 10 hour video of haseul's 16 seconds in EDILY for someone, help

on the weekends sometimes i work on a site that only exists to help people find loona-related social media posts, and now i'm working on a cli to tell me which loona MVs need more attention. i might be a stan.

utah: come to utah, we have snow! that's our only thing, the mountains with the snow!

also utah: IT SNOWED AND WE DON"T KNOW HOW TO HANDLE THAT

i had a dream last night that i had too much garlic. there wasn't anything else notable about the dream, i just had a shitton of garlic for some reason.

i got tired of writing the same ten lines of cluster code over and over so here's a module i published yesterday:
https://www.npmjs.com/package/boring-cluster

just tried to find a "paper box" to buy online because i couldn't remember "filing cabinet" so my sunday is going great

@riking it really is. at one point i tried to figure out how much money we spend on aws and it blew my mind

anyway, that's what i've been up to, hbu?

something like

const App = () => <div>hi i'm a whole page wow</div>

export const mount = ReactDOM.render(<App />, document.getElementById('myelement')

though it might need to be a little more complex.

What this solves: my team focuses on the discovery vertical, your team focuses on the checkout experience, we have separate codebases but our code goes onto the same page. The teams agree on a manifest and who gets what dom node, and that's all you need. Any frontend microservice can use whatever the team wants and implement their own mounting logic. Each app would export itself as default, and its mounting logic.

this probably wouldn't work for a while, because right now `import()` turns into a webpack `require.ensure()` (by babel) which can't take dynamic paths. But it's a nice idea and I think i'm going to mess with it for a bit.

something i've been thinking about:

(async () => {
const manifest = await fetch(config.manifestUrl)
const { apps } = await manifest.json()
Promise.all(apps.map((app) =>
import(app).then(({ default: App, mount }) =>
mount(App))))
})()

A tiny universal frontend microservice loader. There's this thing called Sofe that a local company uses to do something similar, but their lib uses SystemJS, and `import()` is stage-3 so I think it's time to move on from SystemJS.