We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using powerpack-shared-fs-cache in a CI environment (or with CI=1), the cache system:
powerpack-shared-fs-cache
The powerpack-shared-fs-cache should:
Not sure how to do this as it is reliant on a paid feature (powerpack)
Node : 22.8.0 OS : darwin-arm64 Native Target : aarch64-macos pnpm : 9.15.2 nx (global) : 20.1.3 nx : 20.3.0 @nx/js : 20.3.0 @nx/jest : 20.3.0 @nx/eslint : 20.3.0 @nx/workspace : 20.3.0 @nx/cypress : 20.3.0 @nx/devkit : 20.3.0 @nx/esbuild : 20.3.0 @nx/eslint-plugin : 20.3.0 @nx/nest : 20.3.0 @nx/node : 20.3.0 @nx/react : 20.3.0 @nx/vite : 20.3.0 @nx/web : 20.3.0 @nx/webpack : 20.3.0 typescript : 5.7.2 --------------------------------------- Nx Powerpack Licensed to ******* for 5 users in 1 workspace until 11/24/2025 @nx/powerpack-shared-fs-cache : 1.1.1 --------------------------------------- Registered Plugins: @nx/vite/plugin @nx/eslint/plugin @nx/cypress/plugin @nx/webpack/plugin @nx/jest/plugin --------------------------------------- Community plugins: @nxlv/python : 20.3.
No response
The text was updated successfully, but these errors were encountered:
This issue was resolved in the new @nx/powerpack-shared-fs-cache v1.1.2
Sorry, something went wrong.
No branches or pull requests
Current Behavior
When using
powerpack-shared-fs-cache
in a CI environment (or with CI=1), the cache system:Expected Behavior
The
powerpack-shared-fs-cache
should:GitHub Repo
Not sure how to do this as it is reliant on a paid feature (powerpack)
Steps to Reproduce
powerpack-shared-fs-cache
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
The text was updated successfully, but these errors were encountered: