Nylo for VS Code
Utilities for Nylo Flutter projects — a VS Code port of the Nylo
JetBrains/Android Studio plugin.
The extension activates in any workspace folder whose pubspec.yaml lists nylo_framework.
Features
Per-environment run configurations (env-sync)
Scans the project root for .env* files (e.g. .env, .env.dev, .env.prod.staging;
.env-example is ignored) and exposes one Flutter debug configuration per environment.
- Open the Run and Debug dropdown — each environment appears as a launch entry (e.g.
Default, Dev, Prod Staging). No
launch.json is written; the entries are provided
dynamically and always reflect the current .env* files.
- Or run Nylo: Run Environment… from the Command Palette to pick an environment and launch.
Before the app launches, the extension runs Nylo's Metro make:env step for the chosen file
(dart run nylo_framework:main make:env --file=<envfile>), mirroring the JetBrains plugin's
before-run task.
Requires the Dart
/ Flutter extensions
(they provide the dart debug type) and dart on your PATH.
Requires VS Code 1.84 or a later 1.x release. The Marketplace icon is the official Nylo
droplet from the website's public/android-chrome-512x512.png.
The extension identifier is nylo.vscode-nylo; its display name is Nylo for VS Code.
Deferred to a later release
Logs, Localizations and Screenshots views (ports of the JetBrains tool windows) are implemented on
the feature/tool-windows branch, and were held back so the first release ships env-sync alone.
Development
npm install
npm run compile # bundle to dist/extension.js
npm test # run core/ unit tests
Press F5 ("Run Extension") to launch an Extension Development Host.
Packaging and installation
npm ci
npm run check-types
npm test
npx --yes @vscode/vsce package --no-dependencies -o vscode-nylo-0.1.2.vsix
In VS Code, run Extensions: Install from VSIX… from the Command Palette and select
vscode-nylo-0.1.2.vsix. To publish, upload this package at
Manage Extensions. Use New extension →
Visual Studio Code for the first nylo.vscode-nylo release; later releases update that
listing. A previously published nylo.nylo listing is a separate extension, and its
existing installations do not automatically move to the new identifier.