Hacker News Reader

The problem I had was that I was forking a monorepo package, so I had to update its internal dependencies to point to the new place. It's possible I missed something, but I don't think I was able to do this with go.mod.

And yes, manually doing the rename "is fine", but I don't think that has any reason to be stated in a discussion about a refactoring tool.

View on HN

> I don't think that has any reason to be stated in a discussion about a refactoring tool.

Find and replace is the baseline, and for many refactorings is insufficient and fragile, however in replacing a stable, unique, and isomorphic token it is basically as good as it gets, so I think it is relevant. Its probably the least useful thing a refactoring tool could do.

I am not sure. You want to make sure that you are only modifying import statements and those can’t necessarily be identified from just a single line (else you might change an errant URL in a string literal), and you also need to move the files themselves, and update the package line in the files. So sure, you can do it yourself, but why are we building a refactoring tool at all?

Not to mention if the package name itself changes...

Reply on news.ycombinator.com