# What
Some remix templates doesn't package a `vite.config.*` file at their root.
It's the case for the recommended starter "stack" templates: blues-stack, indie-stack and grunge-stack.
As recommended in a TODO comment, it's more suitable to check for a `@remix-run/*` dependency in the package dependencies.
# How
- decouple vite and remix checks
- retrieve the `package.json`
- allow passing a `cwd` to the retrieval method
- remove the "empty config file list" that can be empty for a remix stack
- check that the `package.json` contains a `@remix-run/*` dependency
# Test
Added a fixture by running `npx create-remix@latest --template remix-run/indie-stack` in the [frameworks](/Fluf22/shadcn-ui/tree/fix/cli-remix-detection/packages/cli/test/fixtures/frameworks) folder and named it `remix-indie-stack`, if ever we want another stack as a fixture later
---
Fixesshadcn-ui/ui#4967
Importing `tailwind.css` is incorrect as it will treat that file as a CSS Module, throwing that it has no `default` export.
Instead, the tutorial relies on the import returning a _URL_ to the stylesheet. Adding `?url` to the import specifier is the way to go.
* Adding support for ~ in target specification
* test(shadcn): add a test for srcDir false
* chore: changeset
---------
Co-authored-by: shadcn <m@shadcn.com>
* fix(cli): Ensure .scss files are considered in getTailwindCssFile
- Updated getTailwindCssFile function to include .scss files when checking for Tailwind CSS configuration.
- This change ensures that .scss files are properly identified and handled, improving compatibility with projects using SCSS.
* chore: add changeset
---------
Co-authored-by: shadcn <m@shadcn.com>
#### Summary:
This pull request addresses a documentation error found in the ShadCN website's Toast component example. Specifically, the import route for the hook is incorrect in the example. and fixes [#4816](https://github.com/shadcn-ui/ui/issues/4816)
#### Issue:
Upon reviewing the [ShadCN Toast documentation](https://ui.shadcn.com/docs/components/toast), I found that the import path for the Toast component hook was wrongly mentioned as being located in the `components` folder. According to the `component.json` file, the correct location of the hook is within the `hooks` folder inside the main directory.
#### Fix:
- Corrected the import path in the Toast component example from `components` to `hooks`, as per the `component.json` file structure.
#### Example of Fix:
**Before:**
```js
import { useToast } from "@/components/use-toast";
```
**After:**
```js
import { useToast } from "@/hooks/use-toast";
```
#### Testing:
- Verified that the corrected path resolves correctly.
- Ensured the example works as expected after the change.
#### Impact:
This fix prevents confusion for users following the example and ensures that the import path accurately reflects the project structure, improving the overall developer experience.
