Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

vercel x nx #129

Open
flexbox opened this issue Aug 24, 2023 · 1 comment · May be fixed by #210
Open

vercel x nx #129

flexbox opened this issue Aug 24, 2023 · 1 comment · May be fixed by #210

Comments

@flexbox
Copy link
Owner

flexbox commented Aug 24, 2023

As a dev
I can use the official way to ship nx to vercel
So that I can have benefits like nx affected

https://vercel.com/docs/monorepos/nx#using-nx-ignore
@MatthysDev
Copy link
Collaborator

MatthysDev commented Aug 30, 2024 •
edited
Loading

I don't have any access to vercel so I can't finish this.

@flexbox Can you follow this step https://vercel.com/docs/monorepos/nx#configure-the-@vercel/remote-nx-runner

and add the token in nx.jsonfile

then clear the cache adn rebuild the project with

npx nx reset
npx nx build

MatthysDev added a commit that referenced this issue Aug 30, 2024
@MatthysDev
fix: 🐛 add vercel compatibility with nx
66e327f 
✅ Closes: #129
@MatthysDev MatthysDev linked a pull request Aug 30, 2024 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: 🐛 add vercel compatibility with nx flexbox/weshipit.today
2 participants
@flexbox @MatthysDev