johnsoncodehk

Volar 2.0: The Rewrite

I'm Johnson, the author of Volar (now Vue Language Tools). We released 2.0 in March 2024. This is a look back at what we changed, why, and what it cost.

Why we needed to rewrite

Vetur and Volar v1 implemented Vue's IDE support through the Language Server Protocol. For small and medium projects this worked fine. For larger projects it broke down, and the reason was always the same: memory.

TypeScript Server and the Vue Language Server each kept their own copy of the project's TS AST — every file, every .d.ts in node_modules. When a project pulled in thousands of .d.ts files (common for anything with a big dependency tree), the two processes together could exhaust available memory.

csotiriou

const pkgcloud = require('pkgcloud');
const streamifier = require('streamifier');

module.exports = {

  init(providerOptions) {
    const client = pkgcloud.storage.createClient(providerOptions);
    const options = { container: providerOptions.defaultContainerName }

    const remoteURL = () =>

difosfor

import { customElement, LitElement } from 'lit-element';

type UnpackCustomEvent<T> = T extends CustomEvent<infer U> ? U : never;

// Define custom event types and details here
interface CustomEventMap {
  /**
   * Dispatched when an error occurs.
   */
  'my-error': CustomEvent<{ error: Error }>;

ajfisher

var firmata = require('firmata');
var repl = require('repl');

var board = new firmata.Board('/dev/ttyAMA0',function(err){
//arduino is ready to communicate
	if (err) {
		console.log("err:" + err);
		return;
	}
	console.log("Firmata Firing LEDs");