#What's your current package.json?
1 messages · Page 1 of 1 (latest)
{
"type": "module",
"dependencies": {
"@dagger.io/dagger": "./sdk",
"@datadog/datadog-api-client": "1.23.0",
"@infisical/sdk": "2.2.3",
"@octokit/rest": "^20.1.1",
"luxon": "3.4.4",
"octokit": "4.0.2",
"typescript": "5.4"
},
"devDependencies": {
"@types/luxon": "3.4.2",
"bun-types": "^1.1.10"
},
"scripts": {
"build": "tsc --noEmit",
"develop": "dagger develop --sdk=typescript && yarn install",
"remote": "infisical run --env=internal -- bun scripts/ci.ts",
"local": "infisical run --silent --env=internal -- dagger call --auth=env:INFISICAL_DAGGER_TOKEN",
"local:plain": "infisical run --silent --env=internal -- dagger call --auth=env:INFISICAL_DAGGER_TOKEN --progress=plain"
},
"packageManager": "yarn@4.2.2",
"resolutions": {
"lru-cache": "<10.4.0"
}
}
Oh but you're using yarn v4.2.2
That's why
I still need to get the fix to use the user's pkg manager with the specific version
that doesn't matter since you aren't reading it anyway
Yes but I want to add the feature to read it
it also complains about having the dagger dependency in both dependencies and devDependencies
So I can use corepack if package manager is set to pnpm or yarn
so it doesn't look like thats the package.json that its reading
I don't underrstand why it says so, your dagger deps is in dependencies
do you have a package.json somewhere else?
nope
And what's your dagger version?
.. originally it was in devDependencies with file:sdk. Maybe its reading a cached copy ?
Hmm 0.11.9 set dagger in dependencies
Maybe restart from a clean state?
Are you sure you're engine has this version?
Try init a project somewhere else just to verify?
I've deleted my engine a couple times
a newly inited project works
Here is the trace for the broken one
https://dagger.cloud/Motion/traces/72a4f788eb1a47f37cbc44013b206b28
Deps are set in dependencies https://dagger.cloud/Motion/traces/72a4f788eb1a47f37cbc44013b206b28#7eb83c691f674063
So I don't understand
It looks like something was pulled from cache
Could you try to clean your cache?
how do I do that ?
is there a way to tell which ones were used by dagger ?
Hmm not afaik
ran docker volume prune... same issue though
Can you do a docker ps?
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4ba0c7fe0bf4 registry.dagger.io/engine:v0.11.9 "dagger-entrypoint.s…" 51 seconds ago Up 51 seconds dagger-engine-ceb38152f96f1298
e4ef380fd056 harness/gitness "/app/gitness server" 2 months ago Up 26 hours 3000-3001/tcp, 0.0.0.0:7100->7100/tcp gitness
2b67307a5cb5 postgres:16.1 "docker-entrypoint.s…" 5 months ago Up 26 hours 0.0.0.0:5432->5432/tcp motion-postgres-1
62737eba8e0d slamdev/temporalite:0.3.0 "temporalite start -…" 7 months ago Up 26 hours 0.0.0.0:7233->7233/tcp, 0.0.0.0:8233->8233/tcp temporal
d550096108da redis:6 "docker-entrypoint.s…" 7 months ago Up 26 hours 0.0.0.0:6379->6379/tcp redis
"source": "dagger",
Okay so that's even more confusing.. you did everything good
I've never hit this issue
fresh init is good
I just tried removing the DAGGER_CLOUD_TOKEN in case that was causing issues, but I got the same thing
Hmm
So it's related to something in your repo :/
Do you import an external module?
"dependencies": [
{
"name": "node",
"source": "github.com/dagger/dagger/sdk/typescript/dev/node@9e59bae142f64975b7c9ad851e6bd4901d43513a"
},
{
"name": "notify",
"source": "github.com/gerhard/daggerverse/notify@4ad0f0317fd57c41001b48c5a9a3a49d39e43210"
}
],
that node module seems to be the issue
.. now I just need to figure out where I'm using that
if I remove it, I just get a generic
Error: Unsupported type any
with no indication of where it saw that
Check dag.node?
doesn't look like I'm using that anywhere
notify seems fine
I am running into another issue though
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'graphql-tag' imported from /src/dagger/sdk/index.ts
at packageResolve (node:internal/modules/esm/resolve:853:9)
at moduleResolve (node:internal/modules/esm/resolve:910:20)
at defaultResolve (node:internal/modules/esm/resolve:1130:11)
at nextResolve (node:internal/modules/esm/hooks:749:28)
at resolve (file:///usr/local/lib/node_modules/tsx/dist/esm/index.mjs?1720542440961:2:3893)
at nextResolve (node:internal/modules/esm/hooks:749:28)
at Hooks.resolve (node:internal/modules/esm/hooks:237:30)
at handleMessage (node:internal/modules/esm/worker:199:24)
at Immediate.checkForMessages (node:internal/modules/esm/worker:141:28)
I can get around this one by adding a yarn.lock in the sdk folder and running yarn install on it
that one seems to be caused by the fact that the sdk is using pnp (well a likely suspect anyway)
What's that?
pnp is the default linker for yarn
what should be using type module ?
your current moudle
it already has thta
Hmm
Is there a way to debug the introspector locally ?
It seems like changes that I make to the sdk folder don't get picked up
You'll need to update dagger code then ./hack/dev and use this one
In the dagger repo
It would be great if you could report where the code-gen was failing for things like this
I already return the traces :/
the trace is for the sdk code though.
If you have the Node / Symbol, then you should be able to show where it is coming from