Swingset fails to load components on Windows

[jmfury]

👋 It looks like since globby doesn't support Windows paths (sindresorhus/globby#130 & sindresorhus/globby#127), the globbing and path operations across swingset silently fail on Windows machines.

To be clear, the package still compiles and no errors are thrown, yet when running on Windows, components-loader.js won't find any components to build into Next.js pages.

I've got a branch working that addresses these issues, but it's tricky since globby, path, and webpack need a variety of path styles. I have successfully run the peerComponents example with [some ugly] changes made locally 🎉

I'll have a PR up for this once I do a bit of clean up on my fork 😄

cc: @BRKalow

[jmfury]

Did not see #37 prior to posting this issue 😅

#55 is up now, up to date w/ main