Add support for github.dev
See original GitHub issueProblem
It would be nice to make the Prisma extension compatible with https://github.dev. So far, there’s no syntax highlighting, formatting, etc. for schema.prisma files.
Suggested solution
Make a web extension version. Guide from VS Code docs repo
Alternative
Use GitHub Codespaces where the extension is compatible.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
The github.dev web-based editor - GitHub Docs
The github.dev editor supports VS Code extensions that have been specifically created or updated to run in the web. These extensions are known...
Read more >Fun Things You Can Do With github.dev
With github.dev, you can install the CodeTour extension, which allows you to create and playback guided walkthroughs of a codebase.
Read more >GitHub integration overview - Azure DevOps - Microsoft Learn
Provides support for inviting GitHub account users to collaborate within an Azure DevOps project. For details, see Invite GitHub ...
Read more >Collaborate on GitHub - Visual Studio Code
GitHub is a cloud-based service for storing and sharing source code. Using GitHub with Visual Studio Code lets you share your source code...
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

Found this restriction list https://code.visualstudio.com/api/extension-guides/web-extensions#web-extension-main-file
Here I can see that the most problematic ones are
We would need to
child_process, so probably disabling it in this context or find another implementationI suspect @m-abdelwahab just misunderstood what I wrote. We’ll keep this issue open and around and work on removing the other blockers when we have time and it makes sense from a priority perspective.