fix to execute `npx shadcn@latest` command

[kbwo]

At first, thank you for great extension.

I fixed #3 and #16.

I have done as much testing as possible, but I have concerns regarding the following points related to the changes:

• The distinction between getRootDirPath, getRootDir, and getWorkSpacePath
  • I couldn't infer the intention behind differentiating these functions. As far as I could tell, they probably yield the same result, so I standardized to getRootDir. However, I cannot guarantee that it's functioning as intended.
• I recently discovered this extension, so I'm not sure if it's correct that the @ directory remains after running Initialize shadcn-ui in your project
• This is unrelated to the issue, but there are parts in the changes where the formatting has been altered. (For example, commas that weren't there before have been added.)
  • However, this is due to running eslint --fix.

I apologize, the commits became a bit sloppy because I did this for myself. If you'd prefer separate commits and PRs for each issue, I can resubmit them that way.

[AlemTuzlak]

Thank you so much, can you tell me what you tested on? Windows or mac? Will be testing it myself I already have stuff ready to go to test this out

[kbwo]

@AlemTuzlak Thank you for your quick reply. I tested on Linux. I can also test on a Mac, but I'm currently short on time. If testing on a Mac is necessary, you'll have to wait for a while.

[AlemTuzlak]

@kbwo I'll test on windows would really appreciate mac too! Will try to find someone if you don't have the time

[kbwo]

@AlemTuzlak Sorry for the delay. I have conducted tests on a Mac, and everything was working without issues in both of normal repository and nested directory like monorepo. There were also some parts that seem to be unrelated to the current fixes, but since I am not fully familiar with all the features of this extension, I tested all the things listed under Features in the README. I don't have a Windows machine, so unfortunately, I won't be able to test it on that platform.

[AlemTuzlak]

@kbwo I have the windows machine so I can test it there, and I did, so the #16 is fixed but #3 is not, the issue with #3 was when you run commands in a subdirectory of a monorepo the code is generated on the root of the monorepo instead of the subdirectory, If you look at: https://github.com/Code-Forge-Net/Remix-Forge/compare/main...3-should-be-monorepo-aware I almost got it working but I haven't thoroughly tested every action after this, but the idea should be that the find goes from the current folder upwards instead of the root downwards. Would you mind changing that?

[kbwo]

@AlemTuzlak Ah, I misunderstood the content of the issue #3 a bit. The problem you pointed out was reproducible in my environment as well. It becomes particularly buggy when there are multiple Remix projects in one repository. I will fix the code to resolve the issue. Thank you for your feedback.

[kbwo]

@AlemTuzlak I've changed codes for #3, and tested with repository which has multiple, nested Remix directories.

The idea should be that the find goes from the current folder upwards instead of the root downwards.

I have made changes to the code according to the policy you suggested. One thing to note is that in the case of a monorepo, if the workspace is not the Remix directory, checkRemixVersion will not be triggered upon activate. (This is considering the existence of multiple Remix projects)

I tested on Linux and mac again. I apologize for the inconvenience, but I would like you to confirm that it works on Windows again.

[AlemTuzlak]

@kbwo I am so sorry I've been super busy and had some personal problems lately, I'll be going over this very soon! Thank you again for your work its really appreciated