Wrong build directory when importing ng2-img-cropper about angular2-img-cropper

[cstefanache]

did you checkout the configuration of the plnkr from the readme? https://plnkr.co/edit/V91mKCNkBQZB5QO2MUP4?p=info

[danielserrao]

Yes, I did. I also tried with map "https://npmcdn.com/[email protected]" without success.

[cstefanache]

What is the error message? Do you get a 404?
Are you doing any bundle?
Do you use WebPack?

[danielserrao]

Hey.

I don't get any error in compile time but I cant run the app because the build was done inside a folder that wasn't suppose to.Without importing the ImageCropperComponent the the build folder is:

www
-> build
-> pages
-> routes
....

With the importing I have the following:

www
-> build
-> app
-> pages
-> routes
....

In this last case, the problem is "Failed to load resource: the server responded with a status of 404 (Not Found)" like you asked. In my systemjs, I configure the path app to be www/build, so, I think is normal to have this error.

Yes, I'm using some bundles, that could be the problem? how?

No, we are not using WebPack.

[jurienhamaker]

Any updates? Has this been fixed by recent updates?

[jurienhamaker]

@danielserrao Will close this in a few days if no reply.

[danielserrao]

Hey, not really, I'm doing other tasks now but I will try to solve this in the next days.

[damiansastre]

this is happening to me too.

[cstefanache]

will do a release 0.7 today - please let me know if you still have the problem after the release

[cstefanache]

Closing the issue - new release 0.7.6 was done today with JS files in the package