These are chat archives for ractivejs/ractive

29th
May 2017
Chris Reeves
@evs-chris
May 29 2017 08:23
@fskreuz what did you use to create that gif?
I see some chrome extensions, but none of them appear to be any good
Chris Reeves
@evs-chris
May 29 2017 15:51
alas, I'm a weirdo that uses a Chromebook as my primary personal machine (at least until this ships)
Joseph
@fskreuz
May 29 2017 16:21
Oooh. That's a neat device.
But a few dollars more, you could get the M3 variant of the SP4.
Chris Reeves
@evs-chris
May 29 2017 16:23
I've always been a sucker for a palm top 😀
Joseph
@fskreuz
May 29 2017 16:23
:smile:
Chris Reeves
@evs-chris
May 29 2017 16:24
I've got an i5 SP3, but it's mostly unused because of the awful battery life (comparatively)
also windows
Joseph
@fskreuz
May 29 2017 16:24
hahaha
Chris Reeves
@evs-chris
May 29 2017 16:25
I've always been a fan of kde, and I'm hoping this will finally give me that in a reasonably long lived portable machine
kde dolphin file manager is 👌
to this day I use it to copy files from an smb share to an sftp server inside vnc on my cloud vm
Mark Powell
@mpowell-atomic
May 29 2017 17:32
hi! so excited to see web site updated. looks great! and 0.9 out. thanks for all the hard work! I am having issues with using webpack and ractive-component-loader with ractive 0.9. I am getting this error: "Uncaught TypeError: Ractive.extend is not a function" on this line in the output generated by the ractive-component-loader: "module.exports = Ractive.extend(component.exports);"
In the changelog i see there are warnings about using Ractive extend... is it related to that? Thanks!
Joseph
@fskreuz
May 29 2017 17:32
Hmm... we might want to know what this component.exports contains.
Mark Powell
@mpowell-atomic
May 29 2017 17:33
true. will log that and see what it contains. that sort of Ractive.extend(compont.exports) line is relatively standard in a lot of component loader-y type things though.
this is a link to the source of ractive-component-loader: https://github.com/thomsbg/ractive-component-loader/blob/master/index.js
Joseph
@fskreuz
May 29 2017 17:36
Assuming component.exports is the component.exports of a component file, I don't see anything problematic. A Ractive global without the extend function seems strange though.
If you don't mind, can you also log what Ractive.extend is?
I have this feeling something else in the code is injecting a custom extend property.
Mark Powell
@mpowell-atomic
May 29 2017 17:38
working on it. as a note, it works fine in ractive 0.8 versions but upgrading to 0.9 it doesn't work
Mark Powell
@mpowell-atomic
May 29 2017 17:45
hmm. is something to do with 0.9 being more es2015-ish? not sure how to add screenshots in gitter without hosting them somewhere.
Joseph
@fskreuz
May 29 2017 17:47
You can simply drag the screenshot to gitter and it uploads it for you.
Mark Powell
@mpowell-atomic
May 29 2017 17:47
ah ok!
Joseph
@fskreuz
May 29 2017 17:47
Also... Ractive has always been ES6-ish even before it was trendy. :wink:
An issue with a repro or link to a demo repo would be nice too. That way, we can also look into it.
Mark Powell
@mpowell-atomic
May 29 2017 17:53
Sure. Will work on it. Have screen shots of the Ractive.extend in the mean time.
Ractive.extend.0.8.png
^ 0.8
Ractive.extend.0.9.png
^ 0.9
click through and it's clearer
in 0.8 it is a Ractive function
in 0.9 it's a module with default
Joseph
@fskreuz
May 29 2017 18:00
Are you by any chance using the mjs bundle on the 0.9 one?
Also seeing a var Ractive = ... on the 0.8 shot. Can we get the entire expression on both? It might give a hint as to what got assigned to Ractive.
Mark Powell
@mpowell-atomic
May 29 2017 18:02
oh interesting. not by choice. but i see there is one in the ractive 0.9 package
Joseph
@fskreuz
May 29 2017 18:03
Aha! Webpack might be picking that up. Not sure how Webpack behaves when it sees "jsnext:main": "ractive.mjs", in the package.json.
Mark Powell
@mpowell-atomic
May 29 2017 18:04
as a quick test i deleted the mjs version from the node_modules ractive directory and now it works...
Joseph
@fskreuz
May 29 2017 18:08
Also not sure what Webpack returns when modules call require('ractive'). Assuming it equates to something like import * as Ractive from 'ractive' instead of import Ractive from 'ractive', it might explain why it's returning an object with thedefault property and not the default export (which is the function).
Mark Powell
@mpowell-atomic
May 29 2017 18:09
yeah. sounds about right.
currently i have not been applying babel to packages in the node_modules folder. if i do run babel on node_modules it compiles out fine also.
this gives me something to go on. thanks!
Joseph
@fskreuz
May 29 2017 18:11
:thumbsup:
Mark Powell
@mpowell-atomic
May 29 2017 18:20
on a related but slightly different note: is anyone else using ractive, webpack and components and not using ractive-component-loader? i feel like that every time ractive updates (well, that's a slight exaggeration... the 0.8 update ... :smile: ) i ask about a components loader issue! maybe there is a better way?! i am sure there is!
Chris Reeves
@evs-chris
May 29 2017 19:27
the goal is to have something bundled with the npm module to handle components so that it doesn't break as easily
there's a ractive bin in 0.9 that will assemble components, but I haven't tried to run it through Webpack yet
Mark Powell
@mpowell-atomic
May 29 2017 23:41
that would be great! how would the ractive bin work with webpack? would we need a loader for it?
Chris Reeves
@evs-chris
May 29 2017 23:50
It has importable library bits, so yes, should just be a loader