clasp push not working as expected. Showing error: ENOENT: no such file or directory, open 'package.json'
See original GitHub issue(Note: Non-breaking issues are likely not to be prioritized. Please consider a PR in addition to your issue)
Expected Behavior
Push my clasp local file to Apps Script
Actual Behavior
Show this error: ENOENT: no such file or directory, open ‘package.json’
Steps to Reproduce the Problem
Specifications
- Node version (
node -v
): v14.17.6 - Version (
clasp -v
): 2.4.1 - OS (Mac/Linux/Windows): Windows
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:5
Top Results From Across the Web
npm WARN enoent ENOENT: no such file or directory, open 'C ...
Run this command where "package.json" file exist. even i experience similar problem then i change the folder and got resolve it. for more ......
Read more >If You Use Clasp With Google Apps Script, You Need This ...
When you write your code locally and deploy your Google Apps Script code with clasp, it creates a .clasp.json file that contains the...
Read more >ENOENT No Such File or Directory Open - YouTube
In This Video We Will See How to Fix npm ERR Code ENOENT npm ERR syscall Open Error or ENOENT No Such File...
Read more >Editor not updated after files added/removed via clasp
1. clasp push this is an intermittent problem that can't be reliably reproduced. What is the expected output? What do you see instead?...
Read more >Google Apps Script to Visual Studio Code with Clasp
Is this normal? $ npm install –save @types/google-apps-script npm WARN saveError ENOENT: no such file or directory, open '/Users ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You can fix this by creating an empty package.json file ({}) at the root of your directory
This seems like an unnecessary dependency, is there any reason why clasp needs to use the package.json?