#nxworkspace — Public Fediverse posts

Boost Your Angular Game with Nx Workspace!

Want to scale your Angular apps like a pro? Discover the ultimate step-by-step guide to mastering Nx Workspace - from setup to advanced tips!

• Faster Builds
• Modular Architecture
• Better Developer Experience

Whether you are a solo dev or managing a large team, Nx is a game changer.

📖 Read the full guide now:
https://lnkd.in/duthfGhx

#Angular #angulartips #WebDevelopment #NxWorkspace #codebetter

I'm working on a JS side project to take a break from #dotnet. Tried adding #shadcn to #NextJS in a #NXWorkspace. Shadcn expects both package.json and Next.js in the same place, with Nx package.json is in root while Next.js is in a subfolder. All tutorials on how to get it working seem like magical incantations and they're for a previous version of shadcn and tailwind. Eventually got it to complete init, but had to create an empty vite.config.js in root dir to fool shadcn into installing - will see if it works tomorrow.

So, I need an idea for a side-side project to take a break from JS. Maybe Golang this time?

I'm working on a JS side project to take a break from #dotnet. Tried adding #shadcn to #NextJS in a #NXWorkspace. Shadcn expects both package.json and Next.js in the same place, with Nx package.json is in root while Next.js is in a subfolder. All tutorials on how to get it working seem like magical incantations and they're for a previous version of shadcn and tailwind. Eventually got it to complete init, but had to create an empty vite.config.js in root dir to fool shadcn into installing - will see if it works tomorrow.

So, I need an idea for a side-side project to take a break from JS. Maybe Golang this time?

I'm working on a JS side project to take a break from #dotnet. Tried adding #shadcn to #NextJS in a #NXWorkspace. Shadcn expects both package.json and Next.js in the same place, with Nx package.json is in root while Next.js is in a subfolder. All tutorials on how to get it working seem like magical incantations and they're for a previous version of shadcn and tailwind. Eventually got it to complete init, but had to create an empty vite.config.js in root dir to fool shadcn into installing - will see if it works tomorrow.

So, I need an idea for a side-side project to take a break from JS. Maybe Golang this time?

I'm working on a JS side project to take a break from #dotnet. Tried adding #shadcn to #NextJS in a #NXWorkspace. Shadcn expects both package.json and Next.js in the same place, with Nx package.json is in root while Next.js is in a subfolder. All tutorials on how to get it working seem like magical incantations and they're for a previous version of shadcn and tailwind. Eventually got it to complete init, but had to create an empty vite.config.js in root dir to fool shadcn into installing - will see if it works tomorrow.

So, I need an idea for a side-side project to take a break from JS. Maybe Golang this time?

I'm working on a JS side project to take a break from #dotnet. Tried adding #shadcn to #NextJS in a #NXWorkspace. Shadcn expects both package.json and Next.js in the same place, with Nx package.json is in root while Next.js is in a subfolder. All tutorials on how to get it working seem like magical incantations and they're for a previous version of shadcn and tailwind. Eventually got it to complete init, but had to create an empty vite.config.js in root dir to fool shadcn into installing - will see if it works tomorrow.

So, I need an idea for a side-side project to take a break from JS. Maybe Golang this time?

I've started a #NextJS and #nestjs side project to learn React and TS backend development. It's going great, I've set up an #NXWorkspace, ESLint, Vitest, added multi-stage Dockerfiles, docker-compose, CI pipelines, set up branch protection and pull request policies and absolutely no actual features or UI. Are those practices useful or am I too deeply entrenched in corporate software development?

I've started a #NextJS and #nestjs side project to learn React and TS backend development. It's going great, I've set up an #NXWorkspace, ESLint, Vitest, added multi-stage Dockerfiles, docker-compose, CI pipelines, set up branch protection and pull request policies and absolutely no actual features or UI. Are those practices useful or am I too deeply entrenched in corporate software development?

I've started a #NextJS and #nestjs side project to learn React and TS backend development. It's going great, I've set up an #NXWorkspace, ESLint, Vitest, added multi-stage Dockerfiles, docker-compose, CI pipelines, set up branch protection and pull request policies and absolutely no actual features or UI. Are those practices useful or am I too deeply entrenched in corporate software development?

I've started a #NextJS and #nestjs side project to learn React and TS backend development. It's going great, I've set up an #NXWorkspace, ESLint, Vitest, added multi-stage Dockerfiles, docker-compose, CI pipelines, set up branch protection and pull request policies and absolutely no actual features or UI. Are those practices useful or am I too deeply entrenched in corporate software development?

I've started a #NextJS and #nestjs side project to learn React and TS backend development. It's going great, I've set up an #NXWorkspace, ESLint, Vitest, added multi-stage Dockerfiles, docker-compose, CI pipelines, set up branch protection and pull request policies and absolutely no actual features or UI. Are those practices useful or am I too deeply entrenched in corporate software development?