Issue description
Hello! When I connected snazzy-info-window - build failed.
All folders and files are at their places.
http://prntscr.com/goeisp
Here is part of the log:
angular2 & angular-google-maps version
"angular/core": "4.4.3",
"agm/core": "1.0.0-beta.1",
"agm/snazzy-info-window": "1.0.0-beta.1",
Other information
ERROR in ./node_modules//directives/snazzy-info-window.js
Module not found: Error: Can't resolve 'snazzy-info-window' in 'D:WorkSpaceimproverbrowsernode_modules@agmsnazzy-info-windowdirectives'
resolve 'snazzy-info-window' in 'D:WorkSpaceimproverbrowsernode_modules@agmsnazzy-info-windowdirectives'
Parsed request is a module
using description file: D:WorkSpaceimproverbrowsernode_modules@agmsnazzy-info-windowpackage.json (relative path: ./directives)
Field 'browser' doesn't contain a valid alias configuration
after using description file: D:WorkSpaceimproverbrowsernode_modules@agmsnazzy-info-windowpackage.json (relative path: ./directives)
resolve as module
D:WorkSpaceimproverbrowsernode_modules@agmsnazzy-info-windowdirectivesnode_modules doesn't exist or is not a directory
D:WorkSpaceimproverbrowsernode_modules@agmsnazzy-info-windownode_modules doesn't exist or is not a directory
D:WorkSpaceimproverbrowsernode_modules@agmnode_modules doesn't exist or is not a directory
D:WorkSpaceimproverbrowsernode_modulesnode_modules doesn't exist or is not a directory
D:WorkSpaceimprovernode_modules doesn't exist or is not a directory
Did you install the package snazzy-info-window?
Yes of course. On screenshot you can see package inside node_modules
The screenshot points to @agm/snazzy-info-window. That package has a peer dep of snazzy-info-window, which you seem to be missing.
Thank you very much guys! =)
In conclusion:
Its not very clear that "snazzy-info-window" must be installed separately.
I think it would be better if this "snazzy-info-window" was a piece "@agm/snazzy-info-window".
Any "@agm/snazzy-info-window" way its cant be used as standalone, so why it doesn't have dependence to snazzy-info-window?
Thank your for help!
Best regards!
@Halynsky I can't speak for the author's reasons, but I can guess that it was handled that way so you could update dependency of snazzy-info-window on your own instead of waiting for a patch of the wrapper which will just bump up the dep versions.
Most helpful comment
The screenshot points to
@agm/snazzy-info-window. That package has a peer dep ofsnazzy-info-window, which you seem to be missing.