probablycorey/shrimp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

broken-shrimp #50

Merged
probablycorey merged 3 commits from broken-shrimp into main 2025-12-01 21:49:05 +00:00
Conversation 5 Commits 3 Files Changed 12 +1207 -8
probablycorey commented 2025-11-24 20:22:59 +00:00
Owner
Copy Link

The Shrimp extension was busted because it was importing the prelude (which has bun specific code) and then trying to run it in vscode (which uses node).

Now we pre-generate metadata for what is in the prelude. And now we also have slick autocomplete for prelude functions!

The Shrimp extension was busted because it was importing the prelude (which has bun specific code) and then trying to run it in vscode (which uses node). Now we pre-generate metadata for what is in the prelude. And now we also have slick autocomplete for prelude functions!
CleanShot 2025-11-24 at 12.24.00@2x.png
118 KiB
CleanShot 2025-11-24 at 12.24.00@2x.png
❤️ 1
probablycorey added 2 commits 2025-11-24 20:22:59 +00:00
defunkt commented 2025-11-24 23:14:31 +00:00
Owner
Copy Link

Beautiful!

Beautiful!
defunkt commented 2025-11-24 23:15:23 +00:00
Owner
Copy Link

Should we build this into the CLI so the extension can do something like shrimp --prelude-meta ? I'm just wondering about whether the Shrimp you're using on the CLI will be a different version than the Shrimp in VSCode. Maybe we want to prevent that from happening though.

Should we build this into the CLI so the extension can do something like `shrimp --prelude-meta` ? I'm just wondering about whether the Shrimp you're using on the CLI will be a different version than the Shrimp in VSCode. Maybe we want to prevent that from happening though.
probablycorey added 1 commit 2025-11-25 00:04:08 +00:00
Spike commented 2025-11-25 00:06:16 +00:00
Collaborator
Copy Link

probablycorey: yeah that makes sense. I feel like almost EVERYTHING done in the extension should be done via the shrimp cli. Then things always be in sync.

**probablycorey**: yeah that makes sense. I feel like almost EVERYTHING done in the extension should be done via the `shrimp` cli. Then things always be in sync.
Spike commented 2025-11-25 00:06:21 +00:00
Collaborator
Copy Link

probablycorey:

**probablycorey**:
Spike commented 2025-11-25 00:06:55 +00:00
Collaborator
Copy Link

probablycorey: The UI is a little noisy right now, but we can tweak that.

**probablycorey**: The UI is a little noisy right now, but we can tweak that.
probablycorey merged commit 1fec471da9 into main 2025-12-01 21:49:05 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: probablycorey/shrimp#50
No description provided.
Delete Branch "broken-shrimp"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?