Publish new version for register?

[pspeter3]

No description provided.

[evanw]

I'd like to but the tests aren't passing due to the new changes coming in. I now see four failing tests. @julien-f?

[julien-f]

Unfortunately I don’t have access to a computer this weekend, if you need me it will have to wait Monday.

I suspect #47 or #58.

[julien-f]

We should set up CI to avoid that in the future (will probably set up Travis CI on Monday if you agree).

[pspeter3]

Pull request #47 is the cause for most of the test failures. Removing it only causes one to fail. I'm investigating more now

[pspeter3]

I added a pull request to pass the tests and will follow up with a test for #36

[pspeter3]

And now restored the behavior of #47

[pspeter3]

Now that the pull request is closed, can we push a new version?

[evanw]

I've also got some manual tests for browser-related stuff. I'm not sure if you've been running those too but it looks like the browserify test is failing due to commit b3fd2b9 by @mprobst.

[mprobst]

@evanw any more details on how it fails? npm test succeeds for me, but opening index.html doesn't. How do you run the test?

[evanw]

Sorry, that isn't obvious. Added instructions to the readme: https://github.com/evanw/node-source-map-support/blob/master/README.md#tests. They have to run over the HTTP protocol because the file protocol is hopelessly broken.

[evanw]

Just published as version 0.3.0.

[pspeter3]

The new version seems to no longer work in my code base for reading file maps

[evanw]

@pspeter3 I just merged your pull request and published 0.3.1. Does that fix your issue?