These are chat archives for ractivejs/ractive

14th
Jun 2017
Joseph
@fskreuz
Jun 14 2017 00:22
One of the lesser known features of Ractive is now documented: Argument references ($n) https://ractive.js.org/api/references/#n
Chris Reeves
@evs-chris
Jun 14 2017 00:24
:tada: I think there's an arguments.0 syntax too, but it's been a while since I've looked at that
@kouts 0.9.1 should be available with some changes you were looking for
I'll update the main changelog when I get to a machine with a real keyboard
kouts
@kouts
Jun 14 2017 06:01
thank you @evs-chris :fireworks:
Chris Reeves
@evs-chris
Jun 14 2017 21:02
I've published ractive-bin-loader for those wanting to use webpack with >= 0.9
Joseph
@fskreuz
Jun 14 2017 21:03
:tada:
Chris Reeves
@evs-chris
Jun 14 2017 21:04
there's a small bug in the parser output if you use relaxed partial names
fix is inbound
Joseph
@fskreuz
Jun 14 2017 21:05
Oooh, ES6. Wondering if any of the existing loaders consume ES6 imports/exports. That should be in the TODO list once we get to the plugins. :D
Martin Kolárik
@MartinKolarik
Jun 14 2017 21:08
how is this different/better than rcu-based loaders?
npm says there are at least two that support webpack: https://www.npmjs.com/search?q=ractive-webpack
Joseph
@fskreuz
Jun 14 2017 21:09
For one, your only dependencies are ractive and webpack. :D
Chris Reeves
@evs-chris
Jun 14 2017 21:10
it's a bit simpler than the rcu-based loaders
Joseph
@fskreuz
Jun 14 2017 21:10
It also uses Ractive's bin, which is also in the Ractive package. Will probably get more attention than the other tools.
Chris Reeves
@evs-chris
Jun 14 2017 21:11
yes, much more maintainable and also automatically works with whatever version of ractive you happen to have
it also doesn't necessarily tie you to one component per file and you have full control over the component creation (Ractive.extend({ ... })) process
so if your component has a companion decorator, you can export it too
Martin Kolárik
@MartinKolarik
Jun 14 2017 21:16
if it's much more maintainable then definitely :+1:
Chris Reeves
@evs-chris
Jun 14 2017 21:16
moving the heavy lifting to webpack/rollup for dependencies
Martin Kolárik
@MartinKolarik
Jun 14 2017 21:17
I'm just asking since there's already at least 10 packages doing this kind of thing, so it's getting confusing even for me
Chris Reeves
@evs-chris
Jun 14 2017 21:17
definitely
shooting for simplifying the whole thing by having an "official" component compiler/template parser built into ractive
a build tool/module bundler plugin can then use that from the ractive module that's already sitting in node_modules
Joseph
@fskreuz
Jun 14 2017 21:20
sounds like the beginnings of a monorepo :D
Martin Kolárik
@MartinKolarik
Jun 14 2017 21:21
ok that makes sense