Didn't create package-lock.json

[jankalfus]

I used deyarn, but it didn't create a package-lock.json file. Here's the command output:

> npx deyarn
npx: installed 47 in 5.371s

deyarn...


Removing `yarn.lock`.
Removed `yarn.lock`.

Removing `node_modules`.
Removed `node_modules`.

Installing dependencies with npm; generating `package-lock.json`.


Success!

NEXT STEPS:
  1. Perform any testing to ensure that package updates were not problematic.
  2. Update package.json scripts to use npm if necessary:
     {/*consored*/"}
  3. Update your CI configuration if necessary
  4. Update the README if necessary
    - Add preferred npm-install instruction
    - Update any other Yarn commands to use npm instead
  5. Commit the made changes

I had to run npm install manually after using deyarn to get a package-lock.json file created. It looks like the packages were installed during deyarn use, but the package-lock.json file was not created.

npm version used is 6.4.1 node 10.13.0

[infodusha]

Same issue, looks like 'npm i' command isn't running on windows.