Kevin Ross

Bizarrely, `yarn config` shows opposite of what I have scoped: ```sh ➤ YN0000: npmRegistries Map(1) { 'https://npm.pkg.github.com' => Map(3) { 'npmAlwaysAuth' => false, 'npmAuthIdent' => null, 'npmAuthToken' => '********' }...

Ok, so this seems to look like something attempted to be solved by the deep merge PR from #2106 which was rejected due to major breaking changes? This is a...

Here is a reproduction of apollo failing as a pure ESM library import due to what I believe is the lack of proper `exports` (I could be wrong). Note that...

@MrDoomBringer perhaps a breaking change is necessary. I agree that the apollo packaging is quite unconventional, but regardless, people using ESM are broken because apollo packages are not providing an...

I have the same issue with the latest release including the fix for #55. I'm not clear what the correct `vitest.commandLine` is for a monorepo as my top level script...

My pull request solves this: https://github.com/manlycode/sms-spec/pull/20

My pull request also solves this and passes Travis CI, as well as has additional fixes: https://github.com/manlycode/sms-spec/pull/20

I just ran into the same thing: ``` Bundler could not find compatible versions for gem "rspec-mocks": In Gemfile: sms-spec (~> 0.1.10) ruby depends on rspec (~> 2.11) ruby depends...

@monfresh check my pull request and you can use my git repo in the meantime. https://github.com/manlycode/sms-spec/pull/20

Unfortunately, I'm abandoning `fs-extra` now because we have switched to ESM only. It only showed up at runtime...`TypeError: o.readFileSync is not a function` It would be great if there were...