feat: tw.apply for component like styles

[sastan]

See this #83 (comment) to try it out.

Resolve #73

[coveralls]

Pull Request Test Coverage Report for Build 491375292

• 233 of 234 (99.57%) changed or added relevant lines in 7 files are covered.
• 4 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.2%) to 95.61%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/twind/presedence.ts	90	91	98.9%

Files with Coverage Reduction	New Missed Lines	%
src/css/index.ts	2	96.65%
src/twind/configure.ts	2	97.28%

Totals
Change from base Build 490136107:	0.2%
Covered Lines:	4272
Relevant Lines:	4463

---

💛 - Coveralls

[github-actions]

size-limit report 📦

Path	Size
dist/twind.js	11.9 KB (+3.03% 🔺)

[github-actions]

Try the Preview Package

Official releases are only available on registry.npmjs.org as twind.

This PR has been published to npm.pkg.github.com as @tw-in-js/twind@pr83.

Install/Update

Configure your NPM client (click to expand)

Adjust you .npmrc to use https://npm.pkg.github.com for @tw-in-js

@tw-in-js:registry=https://npm.pkg.github.com

Using the command line:

npm config set @tw-in-js:registry https://npm.pkg.github.com --global

# For npm
npm install --force twind@npm:@tw-in-js/twind@pr83

# For yarn - upgrade implies install
yarn upgrade twind@npm:@tw-in-js/twind@pr83

[sastan]

Docs will follow. The api is as discussed in the issue.

[itsMapleLeaf]

Also, is there any concern with apply overwriting the existing Function.prototype.apply in JS? I suppose call is an alternative, so perhaps not

[itsMapleLeaf]

Is it still pending? Just to make sure

[sastan]

Jep. Working on a initial draft.

[rschristian]

All of this is super nit-picky documentation grammar/capitalization changes. I'll try to run through the other docs at some point too to ensure consistency.

The recurring two are "tailwind" -> "Tailwind" and "css" -> "CSS". Tailwind refers to itself as "Tailwind" and CSS is an acronym, so it should be capitalized.

[sastan]

Also, is there any concern with apply overwriting the existing Function.prototype.apply in JS? I suppose call is an alternative, so perhaps not

That is definitely the case. It may look odd for some developers. What use case would there be to use Function.prototype.apply on tw?

I'm happy to use a different name but i thought we agreed on tw.apply to mirror tailwinds @apply. What other name would you suggest?

[sastan]

All of this is super nit-picky documentation grammar/capitalization changes. I'll try to run through the other docs at some point too to ensure consistency.

That would be great. English is not my native language.

The recurring two are "tailwind" -> "Tailwind" and "css" -> "CSS". Tailwind refers to itself as "Tailwind" and CSS is an acronym, so it should be capitalized.

Jep.

[rschristian]

The recurring two are "tailwind" -> "Tailwind" and "css" -> "CSS". Tailwind refers to itself as "Tailwind" and CSS is an acronym, so it should be capitalized.

Jep.

From a quick scan I do believe most of the other docs already style these two like this. This page is just the odd one out.

[sastan]

@rschristian Thanks for all the suggestion. You made it really easy for me. I just needed to confirm these 🚀

[rschristian]

@rschristian Thanks for all the suggestion. You made it really easy for me. I just needed to confirm these 🚀

NP, glad it could be of use. I do think there's a handful more, probably hidden behind a "Load more..." box.

[itsMapleLeaf]

That is definitely the case. It may look odd for some developers. What use case would there be to use Function.prototype.apply on tw?

I'm happy to use a different name but i thought we agreed on tw.apply to mirror tailwinds @apply. What other name would you suggest?

I agree, and I still think apply is the best name, it just occurred to me and I figured I'd bring it up just in case. I can't think of any cases either 🤷