Chance Strickland

> In such a case, the user will just need to mark the package as "external" (or in Remix case, exclude it from being bundled) and then it should just...

Looks like this PR got borked a bit with some unrelated changes related to `.node` files in https://github.com/remix-run/remix/pull/3234/commits/f724f0aaeaff9bbd30c3d62360409217deb3e20a. Mind fixing those up so we can take a look?

@nicksrandall no worries, I've done the same 😅 Usually happens because you try to fix two issues on the same branch and accidentally end up force-pushing to the wrong one.

I've been meaning to do this but it fell to the bottom of my to-do list. I'll try to get back on it next week if no one else beats...

I'm also running into this. Has anyone found a workaround since the issue was originally raised? https://github.com/Thinkmill/manypkg/blob/b8b914441995ad267a490251d443665fb999e32b/packages/cli/src/checks/INTERNAL_MISMATCH.ts#L23 Starting in the `INTERNAL_MISMATCH` check, simply checking for and stripping the protocol works...

> @chaance is this handled by the new Meta API? 🙏🏼 No. We're aware of this limitation. I'll make sure something is on our roadmap if it isn't already.

`createCookie()` isn't really type-safe, it's basically just a fake promise in this case. Even with encrypted cookies, you still want to validate the input somewhere on your server. My suggestion...

This is definitely a problem with React hydration and extensions/third-party code injecting code that creates a mismatch. I ran a fresh install and couldn't reproduce the console errors in any...

Hi @cmd-johnson -- I'm looking to *finally* get this bad boy finalized and merged. Just a few tiny conflicts as a result of docs being moved around and updated names....

@stepri Mind addressing @jacob-ebey's feedback? We can get this merged after that's done.