Skip to content

use dagger/node#16

Open
kpenfound wants to merge 1 commit intomainfrom
stdlib_node
Open

use dagger/node#16
kpenfound wants to merge 1 commit intomainfrom
stdlib_node

Conversation

@kpenfound
Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: kpenfound <kyle@dagger.io>
@kpenfound kpenfound requested a review from vito April 1, 2026 15:18
"engineVersion": "v0.20.3",
"sdk": {
"source": "github.com/vito/dang/dagger-sdk@352d057a4d4c4d77612104f842671b512495ef30"
"source": "dang"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part's not quite ready for prime time - needs dagger/dagger#12830 first otherwise no checks are loaded (which is why this PR is ✔️)

Could be worth merging anyway and letting it magically un-break in the future when we ship a new engine, if this is all WIP, but yeah

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just realized this is "sdk": { "source": "dang" } instead of "sdk": "dang". Not sure how I messed that up because I did it at the same time as eslint and prettier. Since I merged the PR for eslint and prettier, would that mean the checks for those on the latest commit would be broken?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"sdk": { "source": "dang" } is technically correct and I think what dagger develop will spit back out

Since I merged the PR for eslint and prettier, would that mean the checks for those on the latest commit would be broken?

Yeah - the bug is that the native dang SDK doesn't support detecting @check, so check -l etc. will just be empty

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I probably ran develop on this one before pushing, that makes sense

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

Successfully merging this pull request may close these issues.

2 participants