fix: leaking css affecting buttons outside of the package

[MarkLyck]

Delete tailwind.css from the npm package.

fixes:

#143
#135

[vercel]

@MarkLyck is attempting to deploy a commit to the Elegance Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
novel	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 9, 2023 4:22pm

[steven-tey]

This breaks all the styles for the editor:

[MarkLyck]

@steven-tey doesn't it only break if the application the package is used in, doesn't already have tailwind styles setup?

Otherwise you might have to scope the import to only affect styles within the editor.

For me when I import this package, I get 2 sets of tailwind.css styles, one for my application level tailwind, and one from this package that's leaking and overwriting my other CSS, such as making buttons transparent.

Gotta admit I haven't tried running it in the app/web that's in this repo. I had to fork the project and make a lot of changes to the editor to make it useable for my project.

E.g. I use uploadthing not vercel blob. I removed this extra tailwind.css import, so it doesn't overwrite my other tailwind styles, I removed the AI and feedback features, and changed the styles.

[jonschlinkert]

Having the same issue. This broke styles across our app globally, not just where the component is used. (not the PR, the way it is currently).

Seems like this is a good use case for using a custom prefix with tailwind. Ideally implementors of Novel would be able to customize this prefix as well.

[steven-tey]

This will be fixed when we cut a new version for #161 – shoutout to @eyalcohen4 for the fix!