web apps made simple
London
Joined July 2013
- Tweets982
- Following11
- Followers1.1K
- Likes172
Ractive JS retweeted
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 ❄️
Updates on Flow’s direction and open source engagement
medium.com/flow-type/clarity…
Ractive JS retweeted
$SNTVT will be adopting getuikit.com @getuikit as its new UI Framework paired with ractive.js.org/ @RactiveJS - We are moving in the new UI starting today.
It's a little disjointed from components in the docs at ractive.js.org/api/#content. 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.
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.
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. chrome.google.com/webstore/d…
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.
You can probably reach it with a prefix (../s or ~/). If you have a live example somewhere (perhaps at ractive.js.org/playground or on jsfiddle), I can take a look.
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!
npm install [email protected]
Couple of bugs fixed, a little friendlier to those who use the bin and TypeScript in their build process.
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.
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.
If you use a bundler like rollup or webpack, lots of stuff on npm already has an es6 entry point included in the package and an appropriate entry in the package.json to point to it. See the "module" and "jsnext:main" keys.
Ractive JS retweeted
Really nice @RactiveJS examples and sandbox. dagnelies.github.io/ractive-…