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

[DOCS]: How do i run the vscode extension? #54

Open
1 task done
Franciscorsil opened this issue Feb 14, 2025 · 2 comments
Open
1 task done

[DOCS]: How do i run the vscode extension? #54

Franciscorsil opened this issue Feb 14, 2025 · 2 comments

Comments

@Franciscorsil
Copy link

Enhancement hasn't been filed before.

  • I have verified this enhancement I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

I have no clue on how i can run the extension...
I'd like to learn because this is something i really liked and it could help me understand and remove some of the abstraction in complex shemas.
still i will try to figure it out

@Franciscorsil
Copy link
Author

Ok so, i managed to run the schema visualizer on the browser turns out i just needed to do npx drizzle-lab visualizer.

but now i wanted to run it on vscode itself, im not finding how to do that am i missing something?

@rphlmr
Copy link
Owner

rphlmr commented Feb 14, 2025

👋 Thanks for your interest on this project.
I'm sorry for this bad onboarding experience :/

Developing on the VSCode extension is really not developer-friendly, you have to build before seeing any changes.

Inside the vscode-extension folder, every time you run npm run build, it will trigger turbo to build the drizzle-lab package and copy the build to an expected folder that the extension uses to run the CLI behind the scenes. Then, you have to open vscode-extension/src/extension.ts and start the debug mode (F5). It launches a new VS Code instance with the extension installed.

I'm currently rewriting the entire project (#52) to make it simpler to update and develop.
The visualizer will be rebuilt with Vite, so it will be easy to run in dev mode as a standalone.
It will also be updated to Tailwind 4, and its style and components will be isolated so they don't conflict with the end user's Tailwind styles or the other apps/packages in this repository.

Creating a monorepo like that was a terrible mistake once I decided to start publishing some parts 😵‍💫

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

2 participants