incuca/vue-loopback

A Vue project template with Loopback framework optionally with Vuex, Vue-router, and Auth boilerplaite

vue-loopback's Issues

run dev ?

Hi there,

I see npm run dev in docs but where is it ?

"scripts": {
    "test": "node test.js",
    "lint": "npx eslint ."
},

Is it going to be added or was it there and removed ? dev mode is a useful thing to have you know :D

Documentation for build doesn't complete successfully

Hi, Thank you for your contribution. I think it's a great starting point for using Loopback with Vue.

I cloned the repo and followed the local setup instructions as written. npm run dev works as expected.

When I do the following, I get an error.

1. npm run build
2. cd build
3. npm run start

Ivans-MacBook-Pro:build ivandov$ npm run start

> [email protected] start /Users/ivandov/git/mfaas/test/build
> (type ./build/index.js && node ./build/index.js) || node ./index.js

sh: line 0: type: ./build/index.js: not found
/Users/ivandov/git/mfaas/test/node_modules/loopback-datasource-juggler/lib/mixins.js:50
      throw new Error(errMsg);
      ^

Error: Model "Account" uses unknown mixin: TimeStamp
    at MixinProvider.applyMixin (/Users/ivandov/git/mfaas/test/node_modules/loopback-datasource-juggler/lib/mixins.js:50:13)
    at ModelBuilder.defineClass [as define] (/Users/ivandov/git/mfaas/test/node_modules/loopback-datasource-juggler/lib/model-builder.js:649:27)
    at Function.ModelClass.extend (/Users/ivandov/git/mfaas/test/node_modules/loopback-datasource-juggler/lib/model-builder.js:447:33)
    at Registry.createModel (/Users/ivandov/git/mfaas/test/node_modules/loopback/lib/registry.js:122:25)
    at /Users/ivandov/git/mfaas/test/node_modules/loopback-boot/lib/executor.js:245:24
    at Array.forEach (<anonymous>)
    at defineModels (/Users/ivandov/git/mfaas/test/node_modules/loopback-boot/lib/executor.js:229:23)
    at setupModels (/Users/ivandov/git/mfaas/test/node_modules/loopback-boot/lib/executor.js:197:3)
    at execute (/Users/ivandov/git/mfaas/test/node_modules/loopback-boot/lib/executor.js:40:3)
    at bootLoopBackApp (/Users/ivandov/git/mfaas/test/node_modules/loopback-boot/index.js:154:3)
    at Object.<anonymous> (/Users/ivandov/git/mfaas/test/build/server/server.js:41:28)
    at Module._compile (module.js:649:30)
    at Object.Module._extensions..js (module.js:660:10)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:501:12)
    at Function.Module._load (module.js:493:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `(type ./build/index.js && node ./build/index.js) || node ./index.js `
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/ivandov/.npm/_logs/2018-06-13T17_05_54_865Z-debug.log

Add optional vuex support

The template should ask if user want's to add vuex support.

SASS: Problem with relative path in Windows

There is a problem compiling the client from Windows, causing problems with the relative SASS paths. I've replaced the backslashes on the routes and apparently that solves the problem.

/gulp-task/compiler.js

~line 17

const relativePath = path.relative(
    path.dirname(filePath),
    path.resolve(dirs.srcClient, 'style/global.scss')
).replace(/\\/g,'/'); // Replace backslashes with forward slashes

Add a service that call loopback api as example

For this we gonna need to add a service that call loopback api.

An example of Vue services here: https://github.com/bedakb/vuewp/tree/master/public/app/themes/vuewp/app/services

Add optional auth boilerplate

We should ask user first, if he wants to add authentication boilerplate that automatically adds routes and views related to authentication

Add optional vue-router support

The template creator is already asking if user want's to add vue-router as dependency, we should add support in template itself.

When use import in main.js, It has errors.

When use import in main.js, It has errors.