[v2] Since gatsby@2.0.0-alpha.16, the main package entry point is unavailable

[kripod]

Description

In gatsby@2.0.0-alpha.13, the main entry point is available, but since gatsby@2.0.0-alpha.16, it cannot be found, thus, eslint-plugin-import's import/no-unresolved rule cannot pass.

Environment

• Gatsby version (npm list gatsby): 2.0.0-alpha.32
• gatsby-cli version (gatsby --version): 2.0.0-alpha.32
• Node.js version: 8.11.1
• Operating System: Windows 10 x64

[m-allanson]

The browser.js file was removed in #4887. In the diff you can see the file packages/gatsby/src/browser.js was removed, along with the browser entry from packages/gatsby/package.json. The main entry was left unchanged.

This was replaced with a webpack alias mapping gatsby to .cache/gatsby-browser-entry.js.

I guess this can be fixed by updating main in packages/gatsby/package.json to point to .cache/gatsby-browser-entry.js?

gatsby-browser-entry.js contains uncompiled ES6 and JSX, but I think that'll be fixed by #4402.

[pieh]

Closed by #5481