Cleaning up files after cli move

[simonwalsh]

Just cleaning up the repo of the files that will reside in the project folder instead of the tool

[simonwalsh]

See anything else @nddery ?

[simonwalsh]

Also, I encountered the issue where I need to install all the dependencies of the CLI tool within the child project to be able to run the foobarify-scripts commands... Did you have to do this as well? I feel it is just a matter of pointing to the root of the tool instead of the root of the project's node modules... But maybe it is because we are using link and there is not a real dependency tree there. Unsure!

[nddery]

Cool - thanks for the .gitignore stuff too - and yes, had forgot about the dependencies.. I also think it's because we've used link and the package isn't really in the node_modules directory (when we'd yarn add foobarify it would then also install it's own dependencies so I'm pretty sure this is "normal" right now)..

[simonwalsh]

Perfect, cool! Lemme make sure it runs when duplicating the dependencies into the project and we can figure out the rest once it is a proper npm package... My feeling though is that there has to be a way to do this before going public... Otherwise people would never be able to test stuff before that moment haha...

The answer probably lies somewhere in there https://docs.npmjs.com/private-modules/intro

[nddery]

So it indeed doesn't install the package - yarnpkg/yarn#2914. This yalc tool could come in handy if we don't want to install foobarify deps into the tests projects.

[simonwalsh]

Or from the looks of it, we use npm to link maybe? I will play around with this tomorrow!

[simonwalsh]

npm link does not work any better