-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng serve does not detect changes in routes #4345
Comments
Same as #4338 |
It doesn't work with @ngtools/[email protected] With @ngtools/[email protected] it works fine. |
By me its not detecting changes to all .ts files. |
…iles (angular#4384) Fix WebpackCompilerHost's cache invalidation behavior on Windows systems. Previously, no call to _resolve was made, causing paths with backslashes not to match the file cache. Fixes angular#4422 Fixes angular#4345 Fixes angular#4338
Did anyone try the fix "installing @ngtools/[email protected]" with hot module reloading? |
i tried the |
…iles (angular#4384) Fix WebpackCompilerHost's cache invalidation behavior on Windows systems. Previously, no call to _resolve was made, causing paths with backslashes not to match the file cache. Fixes angular#4422 Fixes angular#4345 Fixes angular#4338
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Versions.
angular-cli: 1.0.0-beta.26
node: 6.9.5
os: win32 x64
@angular/common: 2.4.5
@angular/compiler: 2.4.5
@angular/core: 2.4.5
@angular/forms: 2.4.5
@angular/http: 2.4.5
@angular/platform-browser: 2.4.5
@angular/platform-browser-dynamic: 2.4.5
@angular/router: 3.4.5
@angular/compiler-cli: 2.4.5
Repro steps.
Added a new route in a working module:
const routes: Routes = [
{path: 'travesses', component: TravessesComponent},
{path: 'peres', component: TravessesComponent} <= this is the new one
];
The log given by the failure.
webpack: Compiling...
Hash: 1cb8464dd62798771354
Time: 476ms
chunk {0} main.bundle.js, main.bundle.map (main) 11.4 kB {2} [initial] [rendered]
chunk {1} styles.bundle.js, styles.bundle.map (styles) 9.96 kB {3} [initial]
chunk {2} vendor.bundle.js, vendor.bundle.map (vendor) 3.16 MB [initial]
chunk {3} inline.bundle.js, inline.bundle.map (inline) 0 bytes [entry]
webpack: Compiled successfully.
Accessing the route gets:
EXCEPTION: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'peres'
Error: Cannot match any routes. URL Segment: 'peres'
at ApplyRedirects.noMatchError (http://localhost:4200/vendor.bundle.js:85516:16) [angular]
at CatchSubscriber.selector (http://localhost:4200/vendor.bundle.js:85485:29) [angular]
at CatchSubscriber.error (http://localhost:4200/vendor.bundle.js:68724:31) [angular]
at MapSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at MapSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at MapSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at MapSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at MapSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at MapSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at LastSubscriber.Subscriber._error (http://localhost:4200/vendor.bundle.js:6711:26) [angular]
at LastSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
at MergeAllSubscriber.OuterSubscriber.notifyError (http://localhost:4200/vendor.bundle.js:48223:26) [angular]
at InnerSubscriber._error (http://localhost:4200/vendor.bundle.js:91572:21) [angular]
at InnerSubscriber.Subscriber.error (http://localhost:4200/vendor.bundle.js:6685:18) [angular]
Mention any other details that might be useful.
After stopping ng serve and launching it again the route works as expected.
The text was updated successfully, but these errors were encountered: