[Bug]: Documented CSS import path is incorrect and fails for package consumers

[gupta-8]

Bug Description

The documented stylesheet import path does not match the actual exported build artifact.

The README instructs consumers to import:

import "react-liquid/styles.css";

However, the package export for ./styles.css points to a file that is not generated in the published build output. The built CSS file is emitted as dist/index.css instead, so the documented import fails for consumers.

---

Steps to Reproduce

Steps to reproduce the behavior:

1. Install the package in a consumer project
2. Add the documented stylesheet import:
   import "react-liquid/styles.css";
3. Start the app or run the bundler
4. See the module resolution error for the stylesheet import

---

Expected Behavior

The documented CSS import path should resolve successfully in a consumer project and load the library styles without any manual workaround.

---

Actual Behavior

The import path shown in the README fails because the package export target does not match the actual generated CSS file.

Consumers following the documentation get a module-not-found / export-resolution error instead of working styles.

---

Environment

• OS: Any
• Browser (if applicable): Any
• Node.js version: Any supported version
• Package manager (npm / pnpm / yarn): npm
• react-liquid version: current repository state

---

Screenshots / Logs

If applicable, add screenshots or error logs to help explain your problem.

Example relevant context:

• README documents: import "react-liquid/styles.css";
• package export maps ./styles.css to ./dist/styles.css
• actual generated CSS artifact is dist/index.css

Possible consumer-facing error:
ERR_MODULE_NOT_FOUND
or equivalent bundler import resolution failure.

---

Additional Context

This is both a packaging issue and a documentation issue.

Possible fixes:

• change the build output so the generated file is actually dist/styles.css
• or update the package export to point to the real generated CSS file
• and ensure the README matches the final published import path

The package documentation and package exports should stay aligned so consumers can copy the documented setup without breakage.