fix: TypeScript exports in package.json

[koistya]

import { getTestServer } from "@google-cloud/functions-framework/testing";
//                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
// Cannot find module '@google-cloud/functions-framework/testing' or its corresponding type declarations.ts(2307)

Ref microsoft/TypeScript#33079

[grant]

I'm not sure the syntax here is correct for a fix. Does this work locally?

As a workaround, you can use the following import:

import { getTestServer } from "@google-cloud/functions-framework/build/src/testing";

[grant]

I don't think "types" is valid here.

https://nodejs.org/api/packages.html#package-entry-points

[matthewrobertson]

it is a "community condition definition" https://nodejs.org/api/packages.html#community-conditions-definitions

[koistya]

@grant it works with at least the TypeScript version 4.7.1-rc. Note that tsconfig.json/moduleResolution needs to be set to Node16 or NodeNext for this to work; otherwise it will work exactly as before I believe (not a breaking change).

[TravisSperry]

Running into what might be a related issue with:

import { getTestServer } from '@google-cloud/functions-framework/build/src/testing'

Error: Package subpath './build/src/testing' is not defined by "exports"

This is with a fresh npx gts init

[grant]

This change seems fine. We can go with it and revert if needed.

[dimip1606]

I'm still getting Cannot find module '@google-cloud/functions-framework/testing' or its corresponding type declarations.ts(2307) with v3.1.2 when using

import { getTestServer } from '@google-cloud/functions-framework/testing'

when "moduleResolution": "node" is set in tsconfig.json. Setting "moduleResolution": "NodeNext" fixes it.