Calling the compiler from nodejs (grunt)

[tmeckel]

I'd like to call tsp from a Grunt task. Searched around in the @typespec/compiler package but it seems that the required functions are not exported. Did I miss something?

[timotheeguerin]

they should be, here is an example of our sample snapshot test calling it programmatically

typespec/packages/samples/src/sample-snapshot-testing.ts

Lines 94 to 108 in 60f7bae

	const [options, diagnostics] = await resolveCompilerOptions(host, {
	cwd: process.cwd(),
	entrypoint: sample.fullPath,
	overrides,
	});
	expectDiagnosticEmpty(diagnostics);
	const emit = options.emit;
	if (emit === undefined || emit.length === 0) {
	fail(
	`No emitters configured for sample "${sample.name}". Make sure the config at: "${options.config}" is correct.`,
	);
	}
	const program = await compile(host, sample.fullPath, options);

Please note that typespec compiler and package only use ESM and as we are preparing for 1.0 we are cleaning up which api are exported from the compiler(none of the ones above are affecteced, jjust the ones that shouldn't be used and are exported by mistake)

[tmeckel]

Whoa! Didn't expect an answer that quick! Thanks for pointing me to that example. When I look at the code I almost got it running 😉 the only thing that I couldn't figure out was "How to create a (compiler) host".

There is a createCLICompilerHost function in @typespec/compiler/dist/src/core/cli/utils.d.ts but it's not exported. Or I was to dumb to get the import statement right in my Gruntfile.js.

Will this change in the future, as you talked about that the team plans to cleanup (change) what gets exported towards 1.0 of TypeSpec.

[timotheeguerin]

use NodeHost if you just want to replicate calling the file system. Otherwise creating your own host is at your own risk of breaking in the future as we add new properties to it.

[tmeckel]

YES! Many thanks! That worked 🎉🎉🎉🎉🎉