Skip to content

Publish new version for register? #60

Closed

Description

@pspeter3
No description provided.

Activity

  1. evanw commented on May 16, 2015

    @evanw
    Owner

    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?

  2. julien-f commented on May 16, 2015

    @julien-f
    Collaborator

    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.

  3. julien-f commented on May 16, 2015

    @julien-f
    Collaborator

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

  4. pspeter3 commented on May 16, 2015

    @pspeter3
    ContributorAuthor

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

  5. pspeter3 commented on May 16, 2015

    @pspeter3
    ContributorAuthor

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

  6. pspeter3 commented on May 16, 2015

    @pspeter3
    ContributorAuthor

    And now restored the behavior of #47

  7. pspeter3 commented on May 26, 2015

    @pspeter3
    ContributorAuthor

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

  8. evanw commented on May 27, 2015

    @evanw
    Owner

    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.

  9. mprobst commented on May 27, 2015

    @mprobst
    Collaborator

    @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?

  10. evanw commented on May 28, 2015

    @evanw
    Owner

    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.

  11. evanw commented on May 29, 2015

    @evanw
    Owner

    Just published as version 0.3.0.

  12. pspeter3 commented on May 29, 2015

    @pspeter3
    ContributorAuthor

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

  13. evanw commented on May 30, 2015

    @evanw
    Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions