#I seem to be in daggerverse publish

1 messages ยท Page 1 of 1 (latest)

steady trail
#

@spring patio I updated the engine version. but still running into issues, appears to have more output.

could not load module
I wasn't able to load a module from github.com/levlaz/daggerverse/docusaurus@56bca3891ad8ccfff47a738a4e0fd73cb1852206. Check the logs below for details.

get name: input: moduleSource.asModule resolve: failed to create module: select: failed to update codegen and runtime: failed to diff generated code: select: TODO: cannot diff with different relative paths: "" != "/"
Creating new Engine session... OK!
Establishing connection to Engine... Connected to engine 185710da913438 (version v0.11.3)
OK!
1: in starting session
1: OK!

2: in Query.checkVersionCompatibility
2: 23:48:18 DBG Using development engine; skipping version compatibility check.

3: in starting session
3: OK!

4: in starting session
4: OK!

5: in starting session
5: OK!

6: in exec sh -c if [ -f package.json ]; then  npm install --package-lock-only ./sdk  --dev  && tsx /opt/module/bin/__tsconfig.updator.ts; else cp -r /opt/module/template/*.json .; fi
6: npm
6:  
6: WARN
6:  
6: config dev Please use --include=dev instead.

6: in exec sh -c if [ -f package.json ]; then  npm install --package-lock-only ./sdk  --dev  && tsx /opt/module/bin/__tsconfig.updator.ts; else cp -r /opt/module/template/*.json .; fi
6: up to date, audited 400 packages in 9s
6: 85 packages are looking for funding
6:   run `npm fund` for details
6: found 0 vulnerabilities
spring patio
#

I'm going to update the Daggerverse dagger version too.

#

@steady trail just made the upgrade changes.
running Daggerverse locally
trying to publish locally

#

success. Making PR.

steady trail
#

Yay

#

Thank you ๐Ÿ˜„

#

BTW I think this may have been a TS bug

#

I ported this over to go and it worked with 0.3.0 (I ported to go because I need this to be as fast as possible)

spring patio
#

Now published both ๐Ÿ˜„