cubic-js / cubic-ui Goto Github PK

The recent rework for implicit page endpoints meant that the vue-router no longer lists pages as async components via component: () => import(path).

To fix this, we probably just have to write the routes after overriding the original endpoint tree of the core node.

The devDependency cubic-core was updated from 1.1.4 to 1.1.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

cubic-core is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

See nexus-stats repo. Won't compile unless node-sass and sass-loader is installed on main repository. Should be fixable by passing absolute paths somewhere.

Spams public directory with css files on every file edit, makes HMR impossible, so it only makes sense in production.

Currently we're running the standard setup for HMR by passing a script to the API node that hooks webpack-hot-middleware into the express router stack. It's somewhat hacky though and won't work if the worker and API don't share the disk space (i.e. running one process on another machine)

In other words: Need a way to listen to webpack's HMR events and send them to the browser client via blitz-js-query.

🚨 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 greenkeeper/.

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 App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Should be put in nexus' app.vue instead.

The devDependency cubic-loader was updated from 1.2.0 to 1.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

cubic-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Causes a few issues with loading files otherwise. (Files are written on request, but the request requests them before they're done being written) -> Log issues.
Also don't wanna manually copy the main bundles into dist.

Fork vue-head and adapt it to support SSR.

The devDependency cubic-api was updated from 1.3.1 to 1.3.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

cubic-api is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Instead of re-authenticating, it returns the JWT expiration error. Seems like it's caused by the JWT error being a 200 status code.

🚨 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 greenkeeper/.

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 App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Worker would simply have endpoints for /404, /503, etc. The API would automatically redirect to the according page. If no response from fallback worker arrives (i.e. non set up or actually too busy), display original raw error instead.

See if this is possible. Images on /src/ would then be minified and saved in /dist/ with their matching hash.
Edit: See docs for more information

Tbh, I don't even know how exactly they're not working, but they just don't do what they should. Compare dev builds vs prod builds. Temporary fix:

@keyframes :local(pulse) {
  // ...
}

As suggested here. This seems to be an issue with css-loader, not cubic.

Should be option in vue-loader

All vue/webpack has currently been moved to nexus-stats. Basic default logic which supports the default page (#3) functionality should be merged back as soon as possible.

Consider #1 first, since HMR doesn't work with that plugin.

We simply shouldn't force people to use that progress bar at that very specific component location. Need to find a way to migrate it to app.vue manually.

Means changes won't apply until the next restart after a restart to supposedly apply changes. At the same time we can't wait until the bundle is generated due to downtime.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Changelogs

No idea when this happened. The extractCSS: true option in vue-loader at /webpack/base.config.js causes extract-text-webpack-plugin to throw this error:

 ModuleBuildError: Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin, refer to https://github.com/webpack/extract-text-webpack-p
lugin for the usage example
      at Object.module.exports.pitch (D:\dev\nexus-stats\nexus-stats\node_modules\extract-text-webpack-plugin\loader.js:25:9)
      at runLoaders (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\NormalModule.js:194:19)
      at D:\dev\blitz\blitz-js-view\node_modules\loader-runner\lib\LoaderRunner.js:364:11
      at D:\dev\blitz\blitz-js-view\node_modules\loader-runner\lib\LoaderRunner.js:179:20
      at runSyncOrAsync (D:\dev\blitz\blitz-js-view\node_modules\loader-runner\lib\LoaderRunner.js:143:3)
      at D:\dev\blitz\blitz-js-view\node_modules\loader-runner\lib\LoaderRunner.js:175:3
      at loadLoader (D:\dev\blitz\blitz-js-view\node_modules\loader-runner\lib\loadLoader.js:36:3)
      at iteratePitchingLoaders (D:\dev\blitz\blitz-js-view\node_modules\loader-runner\lib\LoaderRunner.js:169:2)
      at runLoaders (D:\dev\blitz\blitz-js-view\node_modules\loader-runner\lib\LoaderRunner.js:362:2)
      at NormalModule.doBuild (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\NormalModule.js:181:3)
      at NormalModule.build (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\NormalModule.js:274:15)
      at Compilation.buildModule (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\Compilation.js:149:10)
      at factoryCallback (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\Compilation.js:337:12)
      at NormalModuleFactory.create (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\NormalModuleFactory.js:214:25)
      at _this.semaphore.acquire (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\Compilation.js:237:13)
      at Semaphore.acquire (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\util\Semaphore.js:16:4)
      at iteratorFactory (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\Compilation.js:235:20)
      at D:\dev\blitz\blitz-js-view\node_modules\async\dist\async.js:3083:16
      at eachOfArrayLike (D:\dev\blitz\blitz-js-view\node_modules\async\dist\async.js:1003:9)
      at eachOf (D:\dev\blitz\blitz-js-view\node_modules\async\dist\async.js:1051:5)
      at Object.eachLimit (D:\dev\blitz\blitz-js-view\node_modules\async\dist\async.js:3145:5)
      at Compilation.addModuleDependencies (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\Compilation.js:217:12)
      at Compilation.processModuleDependencies (D:\dev\blitz\blitz-js-view\node_modules\webpack\lib\Compilation.js:202:8),

The vue-loader options accept additional keys which modify how loaders are used. Might be a starting point for fixes.