These are chat archives for ractivejs/ractive
import MyComponent from './path/to/MyComponent.html'in your modules when using this. The plugin converts the HTML file into a module, and
MyComponentis the constructor for that component. If you're ending up building "a module a component", SFCs and this plugin might be of use. And I think you can write ES in the
main.jsand a flat directory of component files (which eventually nests).
If you look at the integration page, most, if not all, of them are third-party. Probably 2/3 of those tools have not seen maintenance for 2-3 years. Probably half of them don't work with 0.9, or 0.8 even. If a developer or a tech lead sees that list, they'd probably say "Oh, an actively-developed library with a lot of dead plugins. This is a bad sign, everyone fled. Not good for a long-term project. Let's look at /React/Reactive/Something else 'R' instead."
Our next move should be:
I was hoping that if anyone had time to briefly clone and look at this implementation of Ractive + Rollup you might give me an idea of why this is bad (?)
Very strange approach, seems your "components" is just a template strings and it's wierd. They become a actual Ractive components only in main.js all together and it's wierd too. I never seen something like this before, but for me it's doesn't make sense.
I decided to give a shot at a getting a module bundler working with Ractive
To make any module bundler works with regular Ractive components (not SFC) you just able to use any common config of Webpack or Rollup.