Ideas and upcoming work

[CGNonofr]

I'll share my todo-list here of remaining things to investigate/improve:

• Handle jsonValidation extension point

• Use vscode extensions services => too complicated
  Instead of registering extensions and calling extension points by hands, we should probably rely on extension vscode services.
  It would allow to use the package.nls.json from the extension which is currently ignored

• Make TextMate experimental worker mode work
  using the editor.experimental.asyncTokenization configuration

• Allow to use some vscode component/views

  • File tree
  • CallHierarchy/TypeHierarchy
  • Debug components (variables, call stack, breakpoints...)
  • Extension points

• Localize monaco-editor? (via vscode-loc repo?) + extensions

• Keep css files as assets/enable preserveModules?

• handle extension activation events

• run extensions in workers

• extension sourcemap (or find a way to let the final user minify it?)

• language detection service

• expose node services as an alternative for electron

• ability to respect sidebar position

• improve vscode patch management

• merge as many fixes as possible in the VSCode repo

• find a way to expose default extensions as server extensions

• notebooks

• chat

• change the versioning scheme to be able to release breaking changes safely

• move back to monaco-editor-core? Integrate monaco-editor

• generate extension contribution types from json schemas

• investigate remote explorer contribution

• Find a way make webviews work onthe github pages demo (issue with crossOriginIsolated)

  • service worker
  • switch to netlify

• Support language pack extensions

• Find a way to extract all service identifier without pulling the rest of the code from the modules they are defined into

• deploy demo of pull requests without publishing

• Optimize locales like in VSCode

• User data profile service override

• extensions assets shouldn't be transformed (especially CSS including image assets)

• registered file system provider should use a tree

• Add references section in README

• Transform const enum, remove the need to disable isolatedModules

• Improve rollup treeshaking, rely on new rollup treeshaking features

[brianjenkins94]

How are you currently keeping pace with upstream changes to vscode? What would you improve?

[brianjenkins94]

Putting it in terms of "a feature I'd like to see", it would be great if I could do this:

import { ExtensionHostKind, createModelReference, monaco, registerExtension, vscode } from "monaco-vscode-api";

and have it "just work", but I'm not sure that's realistically possible for (presumably) legal reasons, if not technical reasons.

[CGNonofr]

It's not a fork of VSCode, we just download it, build it and import from it so it's a little bit different. Also we don't need to follow each change to VSCode and we only update once for each release which is less than once per month

[CGNonofr]

Putting it in terms of "a feature I'd like to see", it would be great if I could do this:

import { ExtensionHostKind, createModelReference, monaco, registerExtension, vscode } from "monaco-vscode-api";

and have it "just work", but I'm not sure that's realistically possible for (presumably) legal reasons.

Can you explain what you mean? it's about the import path? their is no legal concern here as everything including VSCode is under MIT license

[brianjenkins94]

What I'm looking for is roughly a pre-compiled vendor bundle I can just use without having to concern myself with all of this (and by extension all of this) but I still want the ability to add/override individual services.

[CGNonofr]

There are plenty of ways of using this library based on your needs, it would be pretty easy to have some kind of "preset" but I'm not sure which one would be more relevant than others