home.social

Search

10 results for “redzimskidev”

  1. redzimski.dev @[email protected] ·

    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?

    #dotnet #shadcn #nextjs #nxworkspace
  2. redzimski.dev @[email protected] ·

    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?

    #dotnet #shadcn #nextjs #nxworkspace
  3. redzimski.dev @redzimskidev ·

    I'm working on a JS side project to take a break from . Tried adding to in a . 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?

    #dotnet #shadcn #nextjs #nxworkspace
  4. redzimski.dev @[email protected] ·

    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?

    #nxworkspace #nextjs #shadcn #dotnet
  5. redzimski.dev @[email protected] ·

    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?

    #dotnet #shadcn #nextjs #nxworkspace
  6. redzimski.dev @[email protected] ·

    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?

    #nextjs #nestjs #nxworkspace
  7. redzimski.dev @[email protected] ·

    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?

    #nextjs #nestjs #nxworkspace
  8. redzimski.dev @redzimskidev ·

    I've started a and side project to learn React and TS backend development. It's going great, I've set up an , 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?

    #nextjs #nestjs #nxworkspace
  9. redzimski.dev @[email protected] ·

    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?

    #nxworkspace #nestjs #nextjs
  10. redzimski.dev @[email protected] ·

    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?

    #nextjs #nestjs #nxworkspace