diff --git a/README.md b/README.md index 8b240e9..bde83f1 100644 --- a/README.md +++ b/README.md @@ -13,9 +13,9 @@

-github release npm version Build Status codecov
-dependencies Status devDependencies Status
-npm downloads Gitter +github release npm version Build Status codecov
+dependencies Status devDependencies Status
+npm downloads Gitter

```html @@ -370,7 +370,7 @@ The value of `title` will be injected into the `%s` placeholder in `titleTemplat Foo Bar - Baz ``` -The property can also be a function (from [v1.2.0](https://github.com/declandewet/vue-meta/releases/tag/v1.2.0)): +The property can also be a function (from [v1.2.0](https://github.com/nuxt/vue-meta/releases/tag/v1.2.0)): ```js titleTemplate: (titleChunk) => { @@ -833,13 +833,13 @@ Just make sure that you're using the function form of `metaInfo`: } ``` -Check out the [vuex-async](https://github.com/declandewet/vue-meta/tree/master/examples/vuex-async) example for a far more detailed demonstration if you have doubts. +Check out the [vuex-async](https://github.com/nuxt/vue-meta/tree/master/examples/vuex-async) example for a far more detailed demonstration if you have doubts. Credit & Thanks for this feature goes to [Sébastien Chopin](https://github.com/Atinux). ## Why doesn't `vue-meta` support `jsnext:main`? -Originally, it did - however, it caused [problems](https://github.com/declandewet/vue-meta/issues/25). Essentially, Vue [does not support](https://github.com/vuejs/vue/issues/2880) `jsnext:main`, and does not introspect for the `default` property that is transpiled from the ES2015 source, thus breaking module resolution. +Originally, it did - however, it caused [problems](https://github.com/nuxt/vue-meta/issues/25). Essentially, Vue [does not support](https://github.com/vuejs/vue/issues/2880) `jsnext:main`, and does not introspect for the `default` property that is transpiled from the ES2015 source, thus breaking module resolution. Given that `jsnext:main` is a non-standard property that won't stick around for long, and `vue-meta` is bundled into one file with no dynamic module internals as well as the fact that if you're using `vue-meta`, you're 99.9% likely to not be using it conditionally - the decision has been made to drop support for it entirely.