chore: replace prettier workspace property

[benmccann]

Make this a bit more generic. I don't know if it's scalable for every adder to add properties to the workspace for each module they might want to detect. This might be a better pattern for community adders to follow and doesn't lock us in to providing that property

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/sveltejs/cli/@svelte-cli/ast-tooling@76

pnpm add https://pkg.pr.new/sveltejs/cli/sv@76

pnpm add https://pkg.pr.new/sveltejs/cli/@svelte-cli/core@76

commit: 196af11

Missed comments

[AdrianGonz97]

Err, one potential issue I just thought of is if the project may live within a monorepo, but it's not actively part of the monorepo. For instance, it's excluded from the pnpm-workspace.yaml file or workspaces: [] glob array.

Also how will this affect our tests? Maybe we should wrap it with a TESTING flag like we do for typescript detection @manuel3108?

[benmccann]

Err, one potential issue I just thought of is if the project may live within a monorepo, but it's not actively part of the monorepo. For instance, it's excluded from the pnpm-workspace.yaml file or workspaces: [] glob array.

I suppose that's possible, but it doesn't seem super common. I don't think we're going to be able to implement that level of detail pre-launch. It seems like something we could come back and do it later if someone runs into it being an issue.

[manuel3108]

Also how will this affect our tests? Maybe we should wrap it with a TESTING flag like we do for typescript detection @manuel3108?

Good point, added a not in #32