Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"vue-cli-service build" does not use specified entry point when using "--target app" #1533

Closed
TAGC opened this issue Jun 10, 2018 · 0 comments

Comments

@TAGC
Copy link

TAGC commented Jun 10, 2018

Version

3.0.0-beta.16

Reproduction link

TAGC/vue-expandable-grid@5928e09

Steps to reproduce

  1. $ npm install
  2. $ npm run build:demo

What is expected?

Given build:demo is defined as vue-cli-service build ... demo/src/main.ts, I expect vue-cli-service overrides the default Webpack entry point with ./demo/src/main.ts.

What is actually happening?

vue-cli-service ignores the specified entry point, using ./src/main.ts instead. This causes the following error to appear:

> vue-cli-service build --target app --name 'vue-infinite-grid' demo/src/main.ts


⠙  Building for production...Starting type checking and linting service...
Using 1 worker with 2048MB memory limit
⠼  Building for production...

Update package.json
 ERROR  Failed to compile with 1 errors                                                                                                                                      04:35:35

This relative module was not found:

* ./src/main.ts in multi ./src/main.ts
 ERROR  Build failed with errors.

vue-cli-service serve respects the custom entry-point, and works correctly. vue-cli-service build also respects the entry-point when using --target lib or --target wc.

If I override the entry property for configureWebpack in vue.config.js, it uses this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant