lukejacksonn / lukejacksonn/monacode

Can I use monacode as an alternative to monaco-editor?

Open
#5 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
170
Forks
11
PR merge metrics
No merged PRs in 30d

Description

First a lot thanks for authoring this great package. It's really much easier to use than monaco-editor 🤣

I'm trying to migrate monaco-editor to monacode because I just cannot build up monaco-editor with esbuild. However I met some problems.

  1. Can I get access to all monaco apis directly? For now I have to do something like import { Uri } from 'monacode/src/monaco/editor/editor.main.js', and that's a little bit annoying.
  2. It seems that some actions are missing. eg. editor.action.goToDefinition

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the package's public exports and the current deep import from monacode/src/monaco/editor/editor.main.js. Compare the exposed Monaco APIs and the implementation of editor.action.goToDefinition, considering the esbuild migration context. Done means the requested APIs are accessible through the supported package entry point and the missing action is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
developer-experience, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.