Does TypeScript SDK interfere with regular typescript code?

[runic raft]

I have an Astro project (https://docs.astro.build/en/getting-started/) that was daggerized. Whenever I ran npm run build to statically build my project, I got a TypeScript error because the command npm run build also runs by default astro check (https://docs.astro.build/en/reference/cli-reference/#astro-check).

I found two solutions:

1. Rename the dagger folder to .dagger, which requires to update the dagger.json accordingly.
2. Include the exclude property in the tsconfig.json file of my project: "exclude": ["dagger"].

Is that the right way to do that or am I missing something?

[silver shoal]

SGTM.. not sure why astro would scan all files withing the root of the project but seems like the .dagger approach seems nice as we're also leveraging on that source directory convention for our own CI as well

[runic raft]

Is .dagger going to be default when dagger init’ing a TypeScript SDK?

[silver shoal]

maybe. There's an issue we're tracking internally about SDK coexistence. cc @acoustic sable

[acoustic sable]

It's going to probably be the next default, but only if you try to init on a directory with existing contents. If it's an empty directory, the default will continue to be ".".

[runic raft]

Makes sense. To daggerize an app, it must first exist, so .dagger makes sense

[karmic dagger]

@runic raft would you mind opening an issue about this? We are tracking all problems related to "co-existence" between Dagger SDK and the host project. I want to make sure we don't drop yours.

[karmic dagger]

btw that should be a public issue I think

[runic raft]

Absolutely! Gonna do it later today or tomorrow. 👍