Fix compile script on Windows

[Arcanemagus]

npm uses a CMD based environment for running scripts on Windows, which has no emulation of the cp command. Bring in a development dependency on cpy-cli and use that in the compile script to allow errorless installation on Windows.

Alternative options:

• Some Grunt script since it is already a dependency?
• copyfiles is more downloaded, but cpy-cli seems to actually duplicate the behavior of cp

Fixes #219.

[Arcanemagus]

WARNING: That looks like an excessive amount of deletions in the package-lock.json to me...

[winstliu]

WARNING: That looks like an excessive amount of deletions in the package-lock.json to me...

Ha, sounds like the same thing as what happened to me in #276. Are you using npm 5.6.0? I think that might fix it.

Also, fixes #219. This will make my life much easier whenever I have to work on text-buffer 😍.

[Arcanemagus]

Are you using npm 5.6.0? I think that might fix it.

I am, so it must not fix it... if it's actually a problem?

PS C:\foo\text-buffer> npm --version
5.6.0
PS C:\foo\text-buffer> node --version
v9.2.1

[Arcanemagus]

Rebased on master, the package-lock.json diff is a lot saner this time around. The majority of the changes to this file are just removing "dev": true from a bunch of packages, the additions for cpy-cli, and updating of superstring to 2.2.17.

[smashwilson]

👍