ngrx / store-devtools

Developer Tools for @ngrx/store
MIT License
325 stars 38 forks source link

1.3.3 errors - RxJs imports causing errors (can't be found in dist) #14

Closed MarkPieszak closed 8 years ago

MarkPieszak commented 8 years ago

Using the devtools as stated, v1.3.3 with 1.3.2 @ngrx/store. It seems to be pointing to node_modules within it's own dist folder?

I believe it's coming from the store/devtools file here: https://github.com/ngrx/devtools/blob/master/src/store/devtools.ts#L4-L8

ERROR in ./~/@ngrx/store/dist/store-backend.js
[1] Module not found: Error: Cannot resolve module 'rxjs/add/operator/let' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/store/dist
[1]  @ ./~/@ngrx/store/dist/store-backend.js 2:0-32
[1] 
[1] ERROR in ./~/@ngrx/devtools/dist/store/devtools.js
[1] Module not found: Error: Cannot resolve module 'rxjs/add/operator/let' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/devtools/dist/store
[1]  @ ./~/@ngrx/devtools/dist/store/devtools.js 3:0-32
[1] 
[1] ERROR in ./~/@ngrx/devtools/dist/monitors/dock-monitor/dock-monitor.js
[1] Module not found: Error: Cannot resolve module 'rxjs/add/observable/merge' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/devtools/dist/monitors/dock-monitor
[1]  @ ./~/@ngrx/devtools/dist/monitors/dock-monitor/dock-monitor.js 11:0-36

Detailed error from Chrome console:

client?e36c:47./~/@ngrx/store/dist/store-backend.js
Module not found: Error: Cannot resolve module 'rxjs/add/operator/let' in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/store/dist
resolve module rxjs/add/operator/let in /Users/mp/GitHub/ngrx-rest-app/node_modules/@ngrx/store/dist
  looking for modules in /Users/mp/GitHub/ngrx-rest-app/node_modules
    resolve 'file' or 'directory' add/operator/let in /Users/mp/GitHub/ngrx-rest-app/node_modules/rxjs
attilacsanyi commented 8 years ago

Same issue with 1.4.0 version: node_modules/@ngrx/store/store-backend.js is missing.

No store-backend.js resource under @ngrx/devtools under node_modules.

shprink commented 8 years ago

Any workaround?

MikeRyanDev commented 8 years ago

This should be fixed in v2. Re-open if you can still reproduce.

Thanks!