Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

EACCES: permission denied

Open
#417 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
cli, tooling

Research direction

Reproduce the reported yo code flow and start at the code:app#writing step, where the permission error occurs while creating /data/sg-ext/sg-dev-helper. Trace why the generator cannot create that directory despite the reported permission changes; done means the extension is generated successfully in the reported setup.

Written by the indexing model from the issue text.

Description

? What type of extension do you want to create? New Extension (JavaScript)
? What's the name of your extension? sg-dev-helper
? What's the identifier of your extension? sg-dev-helper
? What's the description of your extension? 
? Enable JavaScript type checking in 'jsconfig.json'? No
? Initialize a git repository? Yes
? Which package manager to use? npm
✖ An error occured while running code:app#writing
Error code 

EACCES: permission denied, mkdir '/data/sg-ext/sg-dev-helper'
┌───────────────────────────────────────────────────┐
│              yo update check failed               │
│        Try running with sudo or get access        │
│       to the local update config store via        │
│ sudo chown -R $USER:$(id -gn $USER) /root/.config │
└───────────────────────────────────────────────────┘

sudo or chown didn't help, yo code using root account

Dominant language
JavaScript
Stars
1.6k
Forks
262
Avg merge
15d 22h
Merged PRs (30d)
1

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-generator-code

All issues in microsoft/vscode-generator-code

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.