-
Notifications
You must be signed in to change notification settings - Fork 35
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
import problems #55
Comments
I was only using it with Babel until now. (With webpack & browserify) Babel replaces all import / export statements with require / module.exports. |
A solution to this problem could be to run the test multiple times. Once for every environement. Environements:
Would you be able to provide a PR? |
Of course, as soon as I can |
I already had the time to build a solution. I'll provide a PR in a few minutes. I'd be happy if you could test it. |
Great, it seems to be working, thank you very much:) Could you publish it to npm? |
It's published. It may take a few minutes to refresh all npm etc. caches. |
Thank you very much, but I still cannot see the 2.1.4 version in npm. Could you check it please? |
@elmerbulthuis: The npm deployment is failing again on travis. Could you check and deploy 2.1.4? |
@grofzero: Npm still doesn't find |
Hi,
I tried to install the new ES6 module with jspm, but I had some problems with it. The npm version is not the same as the github version and it contains a require statement in the http-interception.js, so it breaks the code, but I didn't have luck with the github version either. In the index.js it tries to load the './http-interception' but it doesn't load the index.js in the http-interception folder instead it tries to load the http-interception.js file which soesn't exist. Could you please fix these problems, or tell me if I'm doing something wrong?
Thank you
The text was updated successfully, but these errors were encountered: