Updated example 2 to use npm link (see readme for set-up instructions)
As part of this, I discovered a type error so I updated package.json to correctly point to the types file in the dist folder we build. This dist folder will be the npm package we publish and the node module that gets installed
As part of the linking, I removed the "link" folder from example 2 and updated the webpack to link the instances of react, react dom, and react query to each other to ensure that there is only one instance of each. This is an issue with npm link where duplicative instances are created and will not affect a production build. So the annoying webpack configs will not affect anyone in production
I also cleaned up extra files in the src folder for our package that we weren't using