Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
📢 Merging monaco repositories
See original GitHub issueIn order to simplify the monaco-editor release process (through automation) we have decided to merge all the various repositories that come together for shipping the npm package monaco-editor.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Creating a monorepo from separate repos (merging ...
The common reason you might want to merge repos into a type of single repo (monorepo) is because you realize changes from one...
Read more >How do you merge two Git repositories? - Stack Overflow
You can merge repository A into a subdirectory of a project B using the subtree merge strategy. This is described in Subtree Merging...
Read more >Merging - chryswoods.com
Merging. One use-case for cloning a repository is so that you can work on the same files from multiple different computers. Another, and...
Read more >How do I block merging pull requests using Codacy as a ...
To block merging pull requests that don't meet the quality standards of your team you must complete these main steps: Adding coverage to...
Read more >Merging two GitHub repositories without losing commit history
We are in the process of merging smaller example code repositories into larger parent repositories on the MDN Web Docs project.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This workflow makes it messy to then to work as part of a library. At that point, I guess the option would be to just wholesale copy/paste the bits I need out of this repo into my project and just put a notice at the top with regards to license. This does answer my question though to avoid having any monaco plugin bits as dependencies unless I was looking to add/use the entire
monaco-editor, and only as an end project, not a library. Thanks for answering the question, good luck with the merge!I’m sorry things are not yet working completely. We are still working on the packaging scripts.