Skip to content

Handling 301 "Moved Permanently" redirects? #143

@lancejpollard

Description

@lancejpollard

If you change the name of your repo, or move it to a different organization, GitHub still allows that URL to work which is nice if you have projects referencing the old repo location. But component fails in this case because it doesn't seem to handle the 301 redirect.

What do you think about adding support for 301 redirects, so this error doesn't occur?

  error : failed to fetch https://raw.github.com/user/repo/master/index.js, got 301 "Moved Permanently"

The reason is, even if I were to update all my projects referencing the old repo location so they pointed to the new location, if anyone was going to try to install/build in the middle of that process, it would fail.

By adding support for 301 redirects, you could be more relaxed about it.

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions