refactor: isolate the googleapis-common module

[JustinBeckwith]

This change entirely isolates the shared code required for all APIs from the rest of the module. It still includes these files in the overall build, but also introduces a lower build specifically for the new module. This is another step on the way to #806.

[alexander-fenster]

I'm mostly concerned about version 0.0.1. Other comments are optional.

[JustinBeckwith]

Thanks @alexander-fenster - all fixed!

[alexander-fenster]

Since we'll eventually have hundreds of npm modules published from this one repo, we'll need to rethink the current model of tagging and releasing based on the tag. I have no idea how exactly it should be done though (probably worth opening a separate issue to discuss future versioning).

[JustinBeckwith]

One step at a time :)

[ofrobots]

Is the idea that googleapis-common would be published as a standalone package, and that this repo is now a monorepo? If so, let's use an established pattern of shared sub-module being in packages/googleapis-common subdirectory rather than ad-hoc src/shared. Have you considered spinning off to a separate repo though? If monorepos are the way to go, have you considered using https://github.com/lerna/lerna?

[ofrobots]

Oh, and next time, can you please sequester autogenerated code changes into a separate commit. Reviewing changes is a lot harder when manual changes are intermixed with gobs of generated changes.

[JustinBeckwith]

Great questions!

Is the idea that googleapis-common would be published as a standalone package, and that this repo is now a monorepo?

YES!

If so, let's use an established pattern of shared sub-module being in packages/googleapis-common subdirectory rather than ad-hoc src/shared.

I'm 100% on board with that. I am trying to make these changes incrementally. Today, the top level build/test/publish commands will continue to work, exactly as they used to. I'd like to propose landing this first, and working towards the properly named packages. Mostly, I'm worried about breaking the top level build.

If monorepos are the way to go, have you considered using https://github.com/lerna/lerna?

Yup! This is a point in time thing. Once I get all the sub-packages working independently, we will remove the top level build and use something like lerna to orchestrate the publish and linking.

Oh, and next time, can you please sequester autogenerated code changes into a separate commit. Reviewing changes is a lot harder when manual changes are intermixed with gobs of generated changes.

Sorry! Will do next time.