Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>advanced-new-fileNew to Visual Studio Code? Get it now.

advanced-new-file

patbenatar

|
324,013 installs
| (25) | Free
Create files anywhere in your workspace from the keyboard
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

VSCode Advanced New File

Travis AppVeyor

Inspired by Sublime's AdvancedNewFile plugin, this adds the ability to create files anywhere in your workspace.

Demo

Features

  • Fuzzy-matching autocomplete to create new file relative to existing path (thanks to JoeNg93 for making it faster)
  • Create new directories while creating a new file
  • Create a directory instead of a file by suffixing the file path with / as in somedirectory/ to create the directory (thanks to maximilianschmitt)
  • Ignores gitignored and workspace files.exclude settings.
  • Additional option of adding advancedNewFile.exclude settings to workspace settings just like native files.exlude except it explicitly effects AdvancedNewFile plugin only. (thanks to Kaffiend)
  • Control the order of top convenient options ("last selection", "current file", etc) via config setting advancedNewFile.convenienceOptions

Configuration Example

"advancedNewFile.exclude": {
  "node_modules": true,
  "node_modules_electron": true,
  "dev": true,
  "dist": true
},
"advancedNewFile.showInformationMessages": true,
"advancedNewFile.convenienceOptions": ["last", "current", "root"]

Usage

  • Command palette: "Advanced New File"
  • Keyboard shortcut: cmd+alt+n (Mac), ctrl+alt+n (Win, Linux)

Keybindings

You can add your own keybinding in your keybindings.json

{
  "key": "ctrl+n", // "cmd+n" on mac
  "command": "extension.advancedNewFile",
}

Notes

Because VSCode extensions don't yet have the ability to do type-ahead autocomplete within the text input box (See https://github.com/Microsoft/vscode/issues/426), we work around this limitation and provide autocomplete using a two-step workflow of selecting existing path, then providing new filename/path relative to the selection.

Contributing

  1. Clone the repo
  2. $ npm install
  3. Add your feature or fix (in src/) with test coverage (in test/)
  4. Launch the extension and do some manual QA (via Debug > Launch Extension)
  5. Run the tests (via Debug > Launch Tests)
  6. Run the linter: npm run lint
  7. Open a PR
  • Contact us
  • Jobs
  • Privacy
  • Terms of use
  • Trademarks
© 2023 Microsoft