8bu posted a new question
I'm having some trouble with bundle files. vendor.js is too big and it's bad for performance, especially Vuetify bundle. I have read this https://vuetifyjs.com/en/framework/a-la-carte and I'm trying to add vuetify-loader as well as import component which be used in project. But after the test build, the bundle size did not decrease any kb. I checked the vuetify.js inside .nuxt folder and the option treeShake was already added. But it may different with the demo I read on Vuetify document. So can this make my bundles size smaller or it's just the same?
gustojs posted a new question
I may be just missing something simple.
npm publish alone gives same result. Can anybody take a look?
The source: https://github.com/gustojs/nuxt-feathers-vuex
Counting objects: 5, done. Delta compression using up to 4 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 652 bytes | 0 bytes/s, done. Total 5 (delta 2), reused 0 (delta 0) remote: Resolving deltas: 100% (2/2), completed with 2 local objects. To https://github.com/gustojs/nuxt-feathers-vuex.git d921ac8..a8c1682 master -> master * [new tag] v0.0.2 -> v0.0.2 npm notice npm notice 📦 [email protected] npm notice === Tarball Contents === npm notice 1.4kB package.json npm notice 188B CHANGELOG.md npm notice 1.1kB LICENSE npm notice 11.0kB README.md npm notice 1.8kB lib/module.js npm notice 382B lib/templates/auth.js npm notice 0 lib/templates/feathers.js npm notice 269B lib/templates/middleware.js npm notice 3.6kB lib/templates/plugin.js npm notice 127B lib/templates/service.js npm notice 244B lib/templates/store.js npm notice 863B lib/templates/verbose.js npm notice === Tarball Details === npm notice name: nuxt-feathers-vuex npm notice version: 0.0.2 npm notice package size: 7.0 kB npm notice unpacked size: 20.9 kB npm notice shasum: f86f6db1c2549551b06ee7ea4eab744f972d1d45 npm notice integrity: sha512-u7MhtuYXWPrpE[...]ukHP3fVGc5WVA== npm notice total files: 12 npm notice + [email protected]0.0.2
The result: no such package exists
greenkeeper[bot] posted a new question
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the
greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the
greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.