Dear Yarn people,

First of all; thank you for all the effort! I love that you guys have a vision of where the whole node package management thing should go to.

After upgrading, I ran into some problems:

• Unclear webpack and vscode solution. Googling the fixes took more effort than expected.
• What files should I ignore in my project? I now have the .pnp.js, .yarnrc.yml, .vscode/pnpify/... files and I don't know which to ignore or keep.
• Consider not using javascript to document whatever is meant to be in .pnp.js since it makes my IDE (vscode) really slow when diffing.
• The whole setup is way too complicated. I get that you want to improve and be innovative, but this is way worse than a folder called node_modules that contains all the modules and a simple lock file.
• After doing the pnpify thing on Windows, some of my filepaths in .yarnrc.yml are only compatible with windows because they use \ in the paths.
• I can't jump to definition for Typescript files because I get this:

Unable to open 'index.d.ts': 
Unable to read file '/Users/XXX/dev/workflow/.yarn/cache/@types-styled-components-npm-4.4.3-dd2b834be1-2.zip/node_modules/@types/styled-components/ts3.7/index.d.ts' 
(Unknown (FileSystemError): 
Error:
ENOTDIR: not a directory, stat '/Users/XXX/dev/workflow/.yarn/cache/@types-styled-components-npm-4.4.3-dd2b834be1-2.zip/node_modules/@types/styled-components/ts3.7/index.d.ts').

Honestly; I don't really care about how my packages are managed as long as I have some form of lock files and installing and linking them doesn't take too long.

My conclusion is; going back to yarn 1.whatever or just installing npm. Again; I appreciate that we're going into a new direction but my experience this far is really really bad.