Skip to content
This repository was archived by the owner on Apr 9, 2022. It is now read-only.

build-optimizer caches node-modules #913

Closed
Flexns opened this issue May 14, 2018 · 0 comments
Closed

build-optimizer caches node-modules #913

Flexns opened this issue May 14, 2018 · 0 comments

Comments

@Flexns
Copy link

Flexns commented May 14, 2018

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Area

- [x] devkit
- [ ] schematics

Versions

Win 10
node: v8.9.4
npm: 6.0.0
angular-devkit/build-optimizer@0.6.1

Repro steps

  1. npm update [dependency-to-update]
  2. ng build --aot --build-optimizer
  3. ng build --aot

The log given by the failure

The build run WITH build-optimizer does NOT include the changes inside the generated vendor.js file.
The build run WITHOUT build-optimizer does include the desired changes.

Desired functionality

build-optimizer should not use cached vendor.js code for updated node-modules

Mention any other details that might be useful

The node-module dependency that i used for the test was build with ng build, then published via NPM to a local Nexus.
It didn't matter whether i changed the whole code or just added a comment, the build with build-optimizer always stayed the same.

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

No branches or pull requests

2 participants