ERROR: @fastly/js-compute not found in package.json.

[timsuchanek]

Version 0.36.0

What happened
Even though I install @fastly/js-compute via yarn, I still get the following error when running fastly compute publish:

ERROR: `@fastly/js-compute` not found in package.json.

To fix this error, run the following command:

        $ npm install --save-dev @fastly/js-compute

Although it's definitely in my package.json and installed.
When I run npm install, it then works.

[Integralist]

Hi @timsuchanek thanks for raising this issue (and thanks for your patience). I've been discussing internally with our team about adding support for Yarn. It's now on our radar and I'll update you once I've got some more feedback. At the moment there doesn't appear to be any serious blockers to implementing this, it's simply a case of getting it prioritised accordingly.

[JakeChampion]

This issue also happens if you have a monorepo where the @fastly/js-compute package is only installed in the root of the monorepo and not in any of the compute-at-edge projects directly

I was looking into how to confidently know if the package is available for use and the solution which works for all package managers and for monorepos/workspaces is to try and require the package and exit with a non-zero code if it failed:

node -e "try {require('@fastly/js-compute');process.exit(0)} catch {process.exit(1)}"

This also works if @fastly/js-compute was globally installed.

We could replace the npm command in this function with the node command:

cli/pkg/commands/compute/language_toolchain_npm.go

Lines 16 to 23 in 28370af

	func checkPackageDependencyExists(name string) bool {
	// gosec flagged this:
	// G204 (CWE-78): Subprocess launched with variable
	// Disabling as the variables come from trusted sources.
	/* #nosec */
	err := exec.Command("npm", "list", "--json", "--depth", "0", name).Run()
	return err == nil
	}

[Integralist]

As of the CLI v1.3.0 (2021-12-01) Yarn should now be supported: #480