Cleanup comment removal + documentation + release

[AndrewRayCode]

Spelling, comments I don't care about anymore, forgot to add error.d.ts apparently, it was getting published, but not in source control!

[davepagurek]

Sounds good, I can also understand the behaviour being potentially confusing, so following Babel's lead makes sense. let me know what you find!

[AndrewRayCode]

It looks like babel does continue to visit the nodes you replace. Here's an example replacing a function call - and it has infinite recursion because it looks like it keeps visitng the replaced node https://codesandbox.io/p/sandbox/ast-forked-r9fpyx?file=%2Fsrc%2Findex.js%3A25%2C33 (warning this codesandbox triggers a maximum call stack)

I think there's another parity change to make for babel, which is the replacer node itself should also get visited, not just its children

[davepagurek]

Ahh ok right, want me to make a PR adjusting my changes from earlier to just traverse the replaced node directly if it exists?

[AndrewRayCode]

@davepagurek if you are up for it that would be great! I was going to look at it this weekend, if you get to it before then that would be awesome. I'll merge rest of the clean-up changes in this PR.

I think there should be a test for the visit behavior explicitly. In the test, do something like visit an identifier, replace it, and verify the replaced node is also visited and that the original node is not visited.