ProtonMail
Add Appstream Metadata file
AppStream allows upstream projects to define metadata about the components they provide using small XML files, metainfo files, which get installed into locations on the client system and are used by distribuors to enhance their metadata.
https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html
It is suggested (but not required) by Flathub to be maintained and controlled in the upstream (this repository).
I have the same issue with a Turborepo using pnpm workspaces on a Mac. The error makes sense cus Transit Nodes have to use the name of a script that does not exist anywhere in the project as mentioned here.
Hoping some sort of whitelist behavior could be added like @jeniabrook mentioned.
Alternatively, it would be nice if we had a certain keyword like transit or topo as a fixed Transit Node name for everyone - as it currently seems too 'vague' to have any random keyword as the Transit Node task name.
For context, this was still an issue with the latest versions - turbo v2.0.9 and the Turborepo LSP VSCode Extension v2.0.0
I don't think this should be a linting rule at all. For example, I have a "deploy" task that runs all the necessary scripts to build a given app. But I have no "deploy" scripts. Turbo supports this behavior—it shouldn't mark it as an error.
Same issue
It's also a little odd that we can "Run" the task via the extension but it's not a "real" task
It's weird that this is still not fixed. I have actually thought that I needed to have each turbo task defined as a package.json task.
