[SOLVED] npm init will not create package.json file

npm init will not create package.json file

test directory is empty and running npm init doesn't create a package.json file.

error below says there's no such directory which is confusing as I'm in said directory when running npm init command.

PS C:\Users\Sayee\OneDrive\Documents\test> npm init

Press ^C at any time to quit.
package name: (test)
version: (1.0.0)
description:
entry point: (index.js)
test command:
git repository:
keywords:
author:
license: (ISC)
About to write to C:\Users\Sayee\OneDrive\Documents\test\package.json:

{
  "name": "test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}


Is this OK? (yes)
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path C:\Users\Sayee\OneDrive\Documents\test\package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\Sayee\OneDrive\Documents\test\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Sayee\AppData\Local\npm-cache\_logs\2021-09-01T19_50_44_400Z-debug.log

Versions:

node v15.5.1
npm v7.4.2

edit:

different error if I manually create an empty package.json file in the directory. Package.json file is not open anywhere and I've tried running terminal as admin.

npm ERR! code EPERM
npm ERR! syscall write
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, write
npm ERR!  [Error: EPERM: operation not permitted, write] {
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'write'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Sayee\AppData\Local\npm-cache\_logs\2021-09-01T23_57_39_015Z-debug.log

Solution

I believe the issue has nothing to do with npm/node, and it might be due to the special filesystem ownership/permission of C:\Users\Sayee\OneDrive\Documents\.