search

roxiness / roxi

34 stars 3 forks source link

ETA for public release? #2

Open madeleineostoja opened 4 years ago

madeleineostoja commented 4 years ago

I’ve been following Roxi’s development closely, and I’m really keen to try it out in production. Is there a rough timeline for a stable public release? I noticed you’re already on v1.x.x, which suggests a stable API? Is documentation the main thing missing?

Also will Roxi have an equivalent to Sapper’s preload function, which gets tree shaken out of clientside code bundles?

jakobrosenberg commented 4 years ago

Hi @seaneking.

ETA: There are public releases ^1.1.2, but they're not considered stable. As for a stable release, there's no ETA yet.

We use semantic-release doesn't use 0 major, hence the 1.x.x releases. An announced will be made once we reach stable.

Preload: Roxi will be using Routify at the core, which provides window.routify.inBrowser to determine which code runs in the browser/server.

If you´re interested Roxi in it's current state, you can try it with:

npx roxi create my-app
madeleineostoja commented 4 years ago

Gotcha, thanks for the thorough reply!

Re: serverside code, will Roxi/Routify provide the inBrowser check as an import or something to check against? Doing a window && window.routify && window.routify.inBrowser check just to split out some SSR deps seems clunky.

jakobrosenberg commented 4 years ago

You don't have to check against window first. It's available in JSDOM. IIRC if (routify.inBrowser) is enough.

I have considered adding a helper. Mainly to run the check before Routify has been initialized.