Gathering detailed insights and metrics for monorepo-next
Gathering detailed insights and metrics for monorepo-next
Gathering detailed insights and metrics for monorepo-next
Gathering detailed insights and metrics for monorepo-next
@prisma/nextjs-monorepo-workaround-plugin
Ensures that your Prisma files are copied
@nrwl/next
The Next.js plugin for Nx contains executors and generators for managing Next.js applications and libraries within an Nx workspace. It provides: - Scaffolding for creating, building, serving, linting, and testing Next.js applications. - Integration wit
@nx/next
The Next.js plugin for Nx contains executors and generators for managing Next.js applications and libraries within an Nx workspace. It provides: - Scaffolding for creating, building, serving, linting, and testing Next.js applications. - Integration wit
create-next-monorepo
cli for creating an nx momo-repository based on the nx-next-starter template
npm install monorepo-next
Typescript
Module System
Min. Node Version
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
10 Stars
1,230 Commits
10 Forks
6 Watchers
18 Branches
18 Contributors
Updated on Jul 13, 2025
Latest Version
13.0.0
Package Id
monorepo-next@13.0.0
Unpacked Size
95.08 kB
Size
22.33 kB
File Count
44
NPM Version
10.8.2
Node Version
20.19.3
Published on
Jul 13, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
18
24
Detach monorepo packages from normal linking. Work on breaking changes while gradually updating consumers.
Each package can have a monorepo-next.config.js
with the following options:
1module.exports = { 2 // Set this to false to opt-out of change detection and versioning. 3 shouldBumpVersion: true, 4 5 // If your package has a build step, your package.json/files array 6 // will be a git-ignored dir, so we can't use that. Use this to 7 // allow us to still find changes to your package. This appends 8 // to your existing NPM tracked files. 9 changeTrackingFiles: ['src/**'], 10}
next [command]
Commands:
next attach [package] attach a package to a detached package to
resume normal linking [aliases: a]
next changed-files [packages..] list changed files
next changed list changed packages
next cycles detect circular references
next defrag synchronize all dependency version
discrepancies
next detach [package] detach a package from normal linking
[aliases: d]
next release release all packages as needed
next run run script against changed packages
Options:
--help Show help [boolean]
--version Show version number [boolean]
next attach [package]
attach a package to a detached package to resume normal linking
Options:
--help Show help [boolean]
--version Show version number [boolean]
next changed-files [packages..]
list changed files
Options:
--help Show help [boolean]
--version Show version number [boolean]
--ext filter by extension [string]
--only-include-releasable If a file was changed that is not published, don't
count it towards a package change.
[boolean] [default: false]
--exclude-dev-changes If a change doesn't affect consumers, like a
monorepo dev dep change or manually bumping an
external dev dep, don't count it towards a package
change. [boolean] [default: false]
--exclude-deleted Excluded deleted files from the changeset.
[boolean] [default: false]
next changed
list changed packages
Options:
--help Show help [boolean]
--version Show version number [boolean]
--only-include-releasable If a file was changed that is not published, don't
count it towards a package change.
[boolean] [default: false]
--exclude-dev-changes If a change doesn't affect consumers, like a
monorepo dev dep change or manually bumping an
external dev dep, don't count it towards a package
change. [boolean] [default: false]
--exclude-deleted Excluded deleted files from the changeset.
[boolean] [default: false]
next cycles
detect circular references
Options:
--help Show help [boolean]
--version Show version number [boolean]
--detect-dev-dependencies, --dev alert when there is a devDependency in the
loop [boolean] [default: false]
next defrag
synchronize all dependency version discrepancies
Options:
--help Show help [boolean]
--version Show version number [boolean]
--include only synchronize a subset of dependencies[array] [default: []]
--exclude ignore a subset of dependencies [array] [default: []]
--out-of-range override ranges that are out of range
[string] [choices: "major", "minor", "patch"]
--dry-run log to console instead of modifying files
[boolean] [default: false]
next detach [package]
detach a package from normal linking
Options:
--help Show help [boolean]
--version Show version number [boolean]
next release
release all packages as needed
Options:
--help Show help [boolean]
--version Show version number [boolean]
--silent Don't print logs and errors
[boolean] [default: false]
--dry-run log to console instead of modifying files
[boolean] [default: false]
--push git push + tags when done
[boolean] [default: true]
--publish npm publish when done
[boolean] [default: true]
--dist-tag publish to a different NPM dist-tag
[string] [default: "latest"]
--bump-in-range-dependencies If a dependency is still in range, and
nothing changed in my package, still bump my
version and the dependency version.
[boolean] [default: true]
--inherit-greater-release-type If a dependency has a greater release type,
bump my package the with the same release
type. [boolean] [default: false]
--exclude-dev-changes If a change doesn't affect consumers, like a
monorepo dev dep change or manually bumping
an external dev dep, don't count it towards
a package change. [boolean] [default: false]
--validate-dependency-visibility Prevent releasing public packages that
depend on private packages.
[boolean] [default: false]
--clean-up-after-failed-push If there's already a new commit on the
remote, clean up the commit and tags that
won't be used [boolean] [default: false]
--scripts Provide scripts to execute for lifecycle
events (prebump, precommit, etc.,)
[default: {}]
--package-files
[array] [default: ["package.json","bower.json","manifest.json"]]
--bump-files
[array] [default: ["package.json","bower.json","manifest.json","package-lock.j
son","npm-shrinkwrap.json"]]
--default-branch [string] [default: "master"]
next run
run script against changed packages
Options:
--help Show help [boolean]
--version Show version number [boolean]
--only-include-releasable If a file was changed that is not published, don't
count it towards a package change.
[boolean] [default: false]
--exclude-dev-changes If a change doesn't affect consumers, like a
monorepo dev dep change or manually bumping an
external dev dep, don't count it towards a package
change. [boolean] [default: false]
--exclude-deleted Excluded deleted files from the changeset.
[boolean] [default: false]
--silent Don't print logs and errors
[boolean] [default: false]
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
packaging workflow detected
Details
Reason
1 existing vulnerabilities detected
Details
Reason
6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Reason
Found 1/18 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More