feat(vite): add option to generate a package.json to build executor

[jwalton9]

Current Behavior

There's currently no way of generating a minimal package.json when using the vite:build executor

Expected Behavior

The ability to generate a package.json including only the dependencies of the project should be enabled by setting generatePackageJson: true in the vite:build executor options

Related Issue(s)

Fixes #

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 8, 2023 2:12pm

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• nx affected -t e2e-macos --parallel=1 --base= --head=
• nx affected --target=e2e --base=ceabe46e89a798cd958d79f1798c5efb511fc88a --head=365a9b4419fe2256c8dccce88f963a65395aff84 --parallel=1
• nx affected --target=test --base=ceabe46e89a798cd958d79f1798c5efb511fc88a --head=365a9b4419fe2256c8dccce88f963a65395aff84 --parallel=1
• nx affected --target=build --base=ceabe46e89a798cd958d79f1798c5efb511fc88a --head=365a9b4419fe2256c8dccce88f963a65395aff84 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files depcheck check-codeowners --parallel=1 --no-dte
• nx affected --target=lint --base=ceabe46e89a798cd958d79f1798c5efb511fc88a --head=365a9b4419fe2256c8dccce88f963a65395aff84 --parallel=3
• nx-cloud record -- nx format:check --base=ceabe46e89a798cd958d79f1798c5efb511fc88a --head=365a9b4419fe2256c8dccce88f963a65395aff84
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[jaysoo]

Hey @jwalton9 thanks for the PR! I think it's a good idea. Let me know if you need more clarification and I can elaborate more.

Since Nx 16 is right around the corner, I think we'll leave this feature out until after the release. It is already a huge release as is.

[jwalton9]

@jaysoo Are we good to go ahead with this change now v16 is out?

[jensbodal]

Fwiw I tried adding this a month ago here #16045 and then three weeks ago with a more generic solution here: #16330. Either way I just want this feature available but seems odd that my first one was just closed without feedback or offer of improving it.

[mandarini]

Hello @jwalton9 ! I'm taking a look at this right now, and if all's well I'll approve and merge, thank you for your contribution!

@jensbodal thank you for your comment! We are trying our best to meet our users needs! However, we did reply to your PR with feedback! :) #16045 (comment) In any case, I am sorry if you felt that your PR was dismissed without a reason, we are trying our best! :)

[mandarini]

Thank you for your PR!

[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.