From 0885365e4e1560f2e08f7f71725e8217cd8ecd41 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Sat, 6 Jan 2018 01:57:51 -0500 Subject: more --- vue-notes.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'vue-notes.md') diff --git a/vue-notes.md b/vue-notes.md index 6e2fe93..870f20a 100644 --- a/vue-notes.md +++ b/vue-notes.md @@ -230,6 +230,26 @@ TODO TODO +Once upon a time, there was library that compiled SFCs in to JS +modules (`vue-component-compiler`); there were a couple of 3rd-party +stand-alone CLI wrappers for it. That compiler got merged in to +`vueify` (the Browserify plugin for SFCs), and even though the +compiler API is still exposed there, other bundler plugins don't share +it. There's a new `vue-component-compiler` being developed, but it's +not ready yet. That means we're left with 3 *separate* SFC +"compilers" that are fairly tightly coupled with the bundle system +they're designed for. I'm sure they don't contain any nasty +differences. + + - WebPack (`vue-loader`): Presumed to be the flagship option. + + - Browserify (`vueify`): Vue 2.5.0 (2017-10-12) added the ability to + write Functional Components as SFCs. That is not yet supported in + vueify. Three months isn't a long time, but we can surmise that + Browserify is a 2nd-class citizen now. + + - Rollup (`rollup-plugin-vue`): + # misc Components don't work by literally registering custom elements with -- cgit v1.2.3