These are chat archives for ractivejs/ractive

20th
Aug 2018
kouts
@kouts
Aug 20 2018 10:51
@evs-chris how can I see that?
kouts
@kouts
Aug 20 2018 16:22
I have updated https://github.com/kouts/ractive-loader-test to demonstrate the issue
Chris Reeves
@evs-chris
Aug 20 2018 17:50
eesh
it looks like webpack sees our check for a node environment (looking at typeof global) and is trying to shim something in in a way that ends up blowing up
I recommend defining ractive as an external module if you can and just linking the script straight to the page
it's more cacheable that way, and should cut down on build time
kouts
@kouts
Aug 20 2018 17:55
In this specific project that this came up I have a "vendors" bundle, I usually link Ractive manually as you are proposing @evs-chris .
Is this something that can be fixed or is there a workaround?
Chris Reeves
@evs-chris
Aug 20 2018 17:59
looks like you can tell webpack to cut it out by adding node: false to your config
Chris Reeves
@evs-chris
Aug 20 2018 18:07
also, you'll need to import Ractive from 'ractive'; in your components, since it's not global
unless you want to make it global from main.js
those two changes, to the webpack config and adding ractive imports, get things running for me in your test repo
kouts
@kouts
Aug 20 2018 18:38
thanks @evs-chris!