Compatibility issues with Nx `v17.0.2`

[github-actions]

Automated tests failed against Nx v17.0.2.
These errors need to be addressed, before v17.0.2 can be supported.

Package	Change
🐋 nrwl/nx	v15.9.2 -> v17.0.2

Release Notes

nrwl/nx v17.0.2

v17.0.2

17.0.2

🩹 Fixes

• core: do not filter updated files when the native watcher is in use (#19757)
• core: ensure require.resolve('nx') resolves correctly (#19800)
• core: negated paths should be considered by prefix migration (#19791)
• core: await output drain before exiting show (#19793)
• core: change the order of watch ignores so that nxignore is the last one added (#19801)
• core: sort all workspace files after combining (#19806)
• core: provide better error message if we cannot read a file when finding imports (#19809)
• misc: publish legacy readmes (#19762)
• nextjs: Custom server should work on fresh applications (#19833)
• react: Update error message for invalid remote name (#19744)
• vite: throw informative error if no vitest config exists (#19819)
• vue: do not generate component in lib by default (#19755)
• vue: drop vue jest dependency (#19756)
• vue: Standalone tsconfig moduleResultion should be node (#19759)
• vue: move vue-tsc in devDependencies (#19772)
• webpack: add back deprecated Stylus support until v18 (#19810)

❤️ Thank You

• Craigory Coppola @AgentEnder
• Jack Hsu @jaysoo
• Jason Jean @FrozenPandaz
• Jonathan Cammisuli
• Katerina Skroumpelou @mandarini
• Nicholas Cunningham @ndcunningham
• Pavel Fedorin

Compare v17.0.2 with v15.9.2

---

Configuration

📅 Schedule: Daily at midnight (UTC).

This issue has been generated by the nx-latest workflow. 🖖