variejs / varie Goto Github PK

I'm getting the following error when running yarn on a fresh Varie project (v0.3.3):

warning "varie-bundler > [email protected]" has incorrect peer dependency "imagemin@^5.0.0"

What do you think of adding a pre-configured socket client to varie?

It appears that running nvm run watch fails in my environment:

npm run watch

> @ watch /Users/mike/Developer/Sites/xxxx
> webpack-dev-server --mode development --hot

clean-webpack-plugin: /Users/mike/Developer/Sites/xxxx/public has been removed.
events.js:165
      throw er; // Unhandled 'error' event
      ^

Error: getaddrinfo ENOTFOUND varie.test
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
Emitted 'error' event at:
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1495:12)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:17)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ watch: `webpack-dev-server --mode development --hot`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/mike/.npm/_logs/2018-07-04T01_48_38_409Z-debug.log

The work-around for me has been to add the localhost IP address to the watch command in packages.json:

    "watch": "webpack-dev-server --mode development --hot --host 127.0.0.1",

When running npmn run watch, the browser tries to open to http://varie.test:3000, but that is not resolvable:

However, accessing the site under http://localhost:3000 works perfectly. Changing the configuration in webpack.config.js to say localhost worked:

  const config = {
    appName: "Varie",
    host: "localhost",

I suppose the presumption here is that the developer has the domain entry in their hosts file. Maybe adding a paragraph to the docs would help those unfamiliar with the project (idiots like me). hehe

Is .env still used, or has configuration been moved elsewhere? I noticed a lot of configuration stuff in webpack.config.js -- is that where everything is? Thanks!

I've noticed that when using a component within a component that sometimes Varie will freak out.

Example being:

Core.vue Layout
    - imports CoreHeader.vue
        - imports CoreNavigation.vue
            - router-link

The above is how I do things outside of Varie and it works just as expected. However Varie claims that <router-link> is not a registered component.

If I do the following instead, it works...

Core.vue Layout
    - router-link (moved up 2 layers)
    - imports CoreHeader.vue
        - imports CoreNavigation.vue

It seems that when I nest <router-link> one additional component layer it is not resolving correctly.

Even placing <router-link> inside of CoreHeader.vue produces the same error.

• Varie Version: 0.3.3
• Node Version: 10.5.0

Description:

I'm working through the documentation to try to get my app started. I was curious about how models are used, and didn't see anything in the documentation, or the varie/varie.io repo. :) Thanks!

Current routes/index.ts

Expectation for going to /people

Would like to see Core absorbed as the primary layout which has a <router-view> loading resources/views/people/layout.vue with its own <router-view> that loads resources/views/people/index.vue.

The current functionality is a bit wonky and depending on how I reference the path within .template() or .route() I am unable to achieve the desired effect.

I can provide a rough outline once I figure it out. Would be nice to have that in the documentation for reference.

$router.route("*", "404");

Whether I put this towards the top or the bottom of my routes/index.ts it is catching too many routes, even routes that are previously specified; before or after does not change.

I can give more info if asked. Just wanted to quickly capture this issue before I forget.

Generated routes are noted as acting weird in a previous issue. This was an additional example of it interfering with linked stylesheets. You'll notice the CSS file loading from /people/css when it should be coming directly from /css.

Current URL

CSS URL

Route Structure

Repository of Issue

Use the issue-route-params branch.
https://github.com/rebz/vuejs-varie/tree/issue-route-params

Routes File

People Index View

Gif of Output

You'll notice in the GIF that it looks like it is outputting the correct view people/view.vue, however the URL is now root with the param appended; e.g., http://varie.test/1. The URL should be http://varie.test:/people/1.

When running varie new xxxx I get the following error if NVM is not installed:

varie new xxxx
✔ Created xxxx
✖ Error: Command failed: cd /Users/mike/Developer/Sites/xxxx && export NVM_DIR="$HOME/.nvm" && [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && nvm use && npm install

this property for catch method is undefined. tried only with dev version

...
.catch(error => {
    this....
})