Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

monaco-editor-wrapper vs @codingame/monaco-editor-wrapper #736

Closed
rubenfiszel opened this issue Aug 24, 2024 · 3 comments
Closed

monaco-editor-wrapper vs @codingame/monaco-editor-wrapper #736

rubenfiszel opened this issue Aug 24, 2024 · 3 comments

Comments

@rubenfiszel
Copy link

Hi, there are 2 libraries with same name but different namespaces.

Can they be both used together (for instance to use the vim keyboard service from '@codingame/monaco-editor-wrapper' ? Why are they separated but have the same name?

@kaisalmen
Copy link
Collaborator

Hi @rubenfiszel they were created independently and had different evolution path. @CGNonofr / @CodinGame one was first and was originally tied to what Codingame does. @CGNonofr correct me if I am wrong. The Typefox one had its root in a web component and evolved into the wrapper and split off @typefox/monaco-editor-react. Both were migrated into this repo at one point.
I don't know if merging them is possible or useful, but maybe we should explain the whereabouts in the history section of he README.

@CGNonofr
Copy link
Collaborator

The CodinGame version of the wrapper is very tied to our needs (including the languages and tools we need). It's open-source because why not, but it wasn't really designed to be generic and to be widely used

@kaisalmen
Copy link
Collaborator

The question was answered. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants