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
npx nx g @nx/node:library libs/lib-test --compiler swc --linter eslint --publishable --unitTestRunner jest --importPath lib-test --strict true --testEnvironment node
npx nx build lib-test
npx nx release --first-release --dry-run
npx nx release publish --dry-run
Publish output
> nx run lib-test:nx-release-publish
📦 [email protected]
=== Tarball Contents ===
230B README.md
228B package.json
=== Tarball Details ===
name: lib-test
version: X.X.X-dry-run
filename: lib-test-X.X.X-dry-run.tgz
package size: 398 B
unpacked size: 458 B
shasum: 50a8271df0617ee1e04442e5051a9170c02b52a5
integrity: sha512-b7mMs/VaZMz7u[...]hyj4YNPDNrziw==
total files: 2
Would publish to https://registry.npmjs.org/ with tag "latest", but [dry-run] was set
—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
NX Successfully ran target nx-release-publish for project lib-test
Current Behavior
I created a Node monorepo specifically to publish libraries. When publishing a library the tarball doesn't include source code files (.js files).
Note that:
libs
Expected Behavior
The tarball should include the source code.
GitHub Repo
https://github.com/rlmcneary2/bug-nx-publish
Steps to Reproduce
npx create-nx-workspace node-pub --preset node-monorepo --docker false --framework none
cd node-pub
npx nx g @nx/node:library libs/lib-test --compiler swc --linter eslint --publishable --unitTestRunner jest --importPath lib-test --strict true --testEnvironment node
npx nx build lib-test
npx nx release --first-release --dry-run
npx nx release publish --dry-run
Publish output
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
I suspect it's because the package.json
files
property is incorrect. Maybe this is the node-standalone configuration?The text was updated successfully, but these errors were encountered: