fix(misc): align nx init package.json scripts handling when deselecting all plugins

[leosvelperez]

Current Behavior

Running nx init and choosing to add any Nx core plugin results in package.json#nx.includedScripts being set, excluding all scripts.
Running nx init and not selecting any Nx core plugin results in package.json#nx being set (no includedScripts) and nx exec -- prepended to the scripts selected as cacheable.

Expected Behavior

Running nx init should always set package.json#nx.includedScripts defaulting to []. When the user doesn't select any plugin and selects some cacheable operations, these will be added to the includedScripts and no nx exec -- will be prepended to any script.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Mar 25, 2024 2:25pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 503128d. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --targets=e2e,e2e-ci --base=9bfdf897be0b54f82e6ca557853319c0b96612bd --head=503128da3484da4d3cbffadbef355633e1e2546e --parallel=1
• nx affected --targets=lint,test,build --base=9bfdf897be0b54f82e6ca557853319c0b96612bd --head=503128da3484da4d3cbffadbef355633e1e2546e --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=9bfdf897be0b54f82e6ca557853319c0b96612bd --head=503128da3484da4d3cbffadbef355633e1e2546e
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=9bfdf897be0b54f82e6ca557853319c0b96612bd --head=503128da3484da4d3cbffadbef355633e1e2546e

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.