Ractive JS

web apps made simple

[Ractive JS @RactiveJS]

pssst... 1.4.0

[Rob Palmer @robpalmer2]

A message from @flowtype

⚠️ Flow prioritizes Facebook needs above everyone else
⚠️ The plan is to add syntax beyond types
⚠️ Contributions from outside Facebook face a rough ride

This may make sense for a mostly internal product.

It's the polar opposite of TypeScript ❄️

[TomMarchi @tommarchi]

$SNTVT will be adopting https://t.co/snbHUSP10p @getuikit as its new UI Framework paired with https://t.co/Au7sZ1ZLuY @RactiveJS - We are moving in the new UI starting today.

[Ractive JS @RactiveJS]

@ceremcem Ah, yes! An e-book of e-stickers!

[Ractive JS @RactiveJS]

@ceremcem Two free copies of both RactiveJS and Svelte? 😁

[Ractive JS @RactiveJS]

@p3k It's a little disjointed from components in the docs at https://t.co/tdTHZTynia. Immediately after that is the section on yielding, which is very helpful for component use. Additional partials can be provided by the user as well, which should be covered in that section.

[Ractive JS @RactiveJS]

@p3k From the template, that would be the {{>content}} partial. You should also be able to get a handle to that partial with this.partials.content from the js side.

[Ractive JS @RactiveJS]

The Ractive Dev Tool Chrome devtools extension has been updated to support Ractive 0.7 through 1.4 (current edge) thanks to @pmekhaeil. It's also compatible with Firefox, though it's not on AMO. https://t.co/b5IGFf7t10

[Ractive JS @RactiveJS]

@tedmilker I would bet some of the breaking changes with reference ambiguity are causing the issue. If you have an example, we'd be happy to take a look.

[Ractive JS @RactiveJS]

@tedmilker You can probably reach it with a prefix (../s or ~/). If you have a live example somewhere (perhaps at https://t.co/ExlKtFZ2RY or on jsfiddle), I can take a look.

[Ractive JS @RactiveJS]

npm install [email protected]

Since we're down to sporadic minor bug fixes, if nothing crops up with this one, then it will become 1.0.0 after an appropriate (read: arbitrary) amount of time. Huzzah!

[Ractive JS @RactiveJS]

@mikemaccana ~array.indexOf(thing) 😁 Feels like home.

[Ractive JS @RactiveJS]

npm install [email protected]

Couple of bugs fixed, a little friendlier to those who use the bin and TypeScript in their build process.

[Ractive JS @RactiveJS]

@mikemaccana Modules in node land were also a bit of a mess last I looked. Hopefully we'll get there soon, but I don't think we're quite there yet.

[Ractive JS @RactiveJS]

@mikemaccana Not strictly necessary, no, but es6 module support in browsers is still very new (it _just_ landed in ff). Bundlers also give you an opportunity to address a few pain points, like aliasing imports, and most will also do bundle splitting with async import.

[Don Vin @Donny_V]

Really nice @RactiveJS examples and sandbox. https://t.co/ydw9N80VV4

[Ractive JS @RactiveJS]

Pretty slick chatty rpc https://t.co/qjY3t0BI5d

[Ractive JS @RactiveJS]

@npmjs is there any caching with `npm show ractive versions --json`? I'm seeing a discrepancy between that and https://t.co/OoitCwSDgP, where the cli is missing the two builds published ~1 day ago.

[Ractive JS @RactiveJS]

@Rich_Harris @wwr @electronjs The dev model is a bit different on the node side, but if you're coming at it from a webapp that wants to play in a bigger sandbox perspective, you may find the nw model more amenable.