Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Voly FE Quick DevNew to Visual Studio Code? Get it now.
Voly FE Quick Dev

Voly FE Quick Dev

Voly Ltd

|
17 installs
| (0) | Free
A quick dev tool to be used in Voly FE codebase (only works on Svelte file and in conjunction with other internal tools)
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

volyfequickdev

Features

This extension is used to help speed up the frontend development process at Voly, ensure that Svelte components are built and served statically, which is then fetched by an internal tool used to load components to the Voly site

Statically served files
Statically served files are accessible from a working workspace

Extension Settings

No settings required

Known Issues

  1. UI-Loader will always fetch the endpoint on page load, need to add something to the Voly system as a flag to ensure it only makes call when necessary

Release Notes

1.0.0

  • Making use of rollup build in watch mode, the extension listens on document save event to trigger 2 commands to generate instantiation scripts and build the corresponding components.
  • The Folder Explorer section from the activity bar provides a mini workspace to keep track of built files, and an ability remove them if necessary.
  • The Extension Settings section allows dev to close and reopen the server, globally activate and deactivate the extension.
  • The Shareable Local Connection section allows frontend dev to connect to another dev - specifically a backend dev - to transfer built component files (share their local with others) and changes can then be seen by both parties. This is currently limited to one connection per dev.

1.1.0

  • In the previous version, there was a lackage of deep trace for sources of import, meaning once the extension finds component(s) that is / are importing the saved file, the operation terminates regardless of any valid instantiation comment. We will now have an ability to traverse deeper into the sources of import when a saved file is a child component whose immediate parent component does not contain an instantiation comment.

1.1.1

  • Cleanup code.

1.1.2

  • Fixed issue with duplicate components to be instantiated and built in different terminal instances. This was due to not checking the visited paths and active terminal IDs when brute-force finding instantiables and tracing for sources of import.

1.1.3

  • Update finding instantiables logic to ensure same component can be re-instantiated if the terminal process for it has been terminated.

1.1.4

  • Prioritise the results of the trace for import sources over ones of brute-force finding instantiables.

1.1.5

  • Change server provider from Express to Koa for its lightweight dependencies and bundleable-ness with webpack.

1.1.6

  • Allow all methods (the preflight request - OPTIONS - was blocked due to the setup in the allowed methods option for Koa server).

1.2.0

  • Handle the opening and closing of the new secure network protocol (https) for touchscreen device testing.
  • Update the exclusion list to inclusion list of repo names that are a target for the extension to run on.
  • Update the extension server to extend port option range and allow requests coming from voly.docker URL.

1.2.1

  • Cert keys are no longer part of the extension, instead the extension will look for them in target repos it can run on.

1.2.2

  • Allow docker environment in our server whitelist.

1.3.0

  • Use Ngrok to globalise a local dev environment to other devs (mainly for BE team) for a quick collaborative testing environment.

1.3.2

  • Implement tree item removal and URL copying from the UI.

1.3.3

  • Encountered an issue with Ngrok not returning the content-type right for the css and js files, hence use LocalTunnel and Serveo SSH as an alternative.

1.3.4

  • Buffer data from node's data emit event so that a valid URL from Serveo SSH is always returned.

1.3.5

  • Fix issue with not being able to remove a Serveo SSH tunnel after using Serveo and LocalTunnel methods respectively.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft