You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Call libraryGenerator from @nx/react in your local generator
Run jest with the default jest.config.ts generated by the @nx/plugin generator generator
Nx Report
> NX Report complete - copy this into the issue template
Node : 18.16.0
OS : darwin arm64
pnpm : 6.10.1
Hasher : Native
nx (global) : 16.0.2
nx : 16.3.1
@nx/js : 16.3.1
@nx/jest : 16.3.1
@nx/linter : 16.3.1
@nx/workspace : 16.3.1
@nx/cypress : 16.3.1
@nx/devkit : 16.3.1
@nx/eslint-plugin : 16.3.1
@nx/plugin : 16.3.1
@nx/react : 16.3.1
@nx/rollup : 16.3.1
@nx/storybook : 16.3.1
@nrwl/tao : 16.0.2
@nx/webpack : 16.3.1
typescript : 4.8.4
---------------------------------------
Local workspace plugins:
[REMOVED as these are enterprise packages]
---------------------------------------
The following packages should match the installed version of nx
- @nrwl/[email protected]
To fix this, run `nx migrate [email protected]`
Failure Logs
No response
Operating System
macOS
Linux
Windows
Other (Please specify)
Additional Information
The exact same problem, but on a different package is described in #12145. Is there a reason why we're using schema.d.ts instead of schema.ts files? Looks like the tooling is treating it as a JS file and creating a broken entrypoint for it?
The text was updated successfully, but these errors were encountered:
Current Behavior
A
schema.d.ts
is being exported. Breaksjest
Here's a patch that fixes it:
Expected Behavior
A
schema.d.ts
would NOT be exportedGitHub Repo
No response
Steps to Reproduce
libraryGenerator
from@nx/react
in your local generatorjest
with the defaultjest.config.ts
generated by the@nx/plugin
generator generatorNx Report
Failure Logs
No response
Operating System
Additional Information
The exact same problem, but on a different package is described in #12145. Is there a reason why we're using
schema.d.ts
instead ofschema.ts
files? Looks like the tooling is treating it as a JS file and creating a broken entrypoint for it?The text was updated successfully, but these errors were encountered: