Here I mapped a custom package.json nested inside a package to the file that they would resolve to

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I actually added the rule. Docs here

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

cc @michal

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

Here I mapped a folder to the index.js file within

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I mapped a folder to the index.js file within

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

This mapped to a custom package.json nested inside a package. It resolves to a .tsx file, but when I tried to import that directly, Metro became unhappy. I opted to just ignore the ESLint rule, as native is not impacted by either the Node.js 19 or Webpack 5 migrations

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

I am honestly not sure why this was missed in the script from D6692

Here I mapped a folder to the index.js file within

Here I mapped a folder to the index.js file within

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

My script in D6692 missed these because they are import statements, not export statements. The blog post that inspired my codemod script warned that this would happen!

This was missed in D6692 because it is a require statement, not an import

This was missed in D6692 because it is a require statement, not an import

Here I mapped a folder to the index.js file within

Oops, this is duplicated now on line 40. Will remove the duplicate before landing

Here I mapped a folder to the index.js file within

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I actually added the rule. Docs here

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

cc @michal

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

Here I mapped a folder to the index.js file within

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I mapped a folder to the index.js file within

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

This mapped to a custom package.json nested inside a package. It resolves to a .tsx file, but when I tried to import that directly, Metro became unhappy. I opted to just ignore the ESLint rule, as native is not impacted by either the Node.js 19 or Webpack 5 migrations

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

I am honestly not sure why this was missed in the script from D6692

Here I mapped a folder to the index.js file within

Here I mapped a folder to the index.js file within

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

My script in D6692 missed these because they are import statements, not export statements. The blog post that inspired my codemod script warned that this would happen!

This was missed in D6692 because it is a require statement, not an import

This was missed in D6692 because it is a require statement, not an import

Here I mapped a folder to the index.js file within

Here I mapped a folder to the index.js file within

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I actually added the rule. Docs here

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

cc @michal

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

Here I added an eslint-disable. I could not find a JS file this corresponds to, and it is probably some Electron magic that cannot be changed.

I opted to just ignore the ESLint rule, as desktop is not impacted by either the Node.js 19 or Webpack 5 migrations.

Here I mapped a folder to the index.js file within

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I mapped a folder to the index.js file within

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that

wagmi declares these as exports on its package.json, so Webpack is okay with it

This mapped to a custom package.json nested inside a package. It resolves to a .tsx file, but when I tried to import that directly, Metro became unhappy. I opted to just ignore the ESLint rule, as native is not impacted by either the Node.js 19 or Webpack 5 migrations

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

I am honestly not sure why this was missed in the script from D6692

Here I mapped a folder to the index.js file within

Here I mapped a folder to the index.js file within

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

My script in D6692 missed these because they are import statements, not export statements. The blog post that inspired my codemod script warned that this would happen!

This was missed in D6692 because it is a require statement, not an import

This was missed in D6692 because it is a require statement, not an import

Here I mapped a folder to the index.js file within

Here I mapped a folder to the index.js file within

Here I mapped a custom package.json nested inside a package to the file that they would resolve to

Here I added an eslint-disable. When I tried to map this to a file, Webpack 5 became unhappy that the file was not specified in exports in react-dom's package.json. I tried Googling but couldn't find a quick solution. Ultimately the unqualified import works fine with Webpack 5 so we're keeping that