Makes tailwind config settings easier.

[doong-jo]

Hello, thank you for your outstanding results.

The way to create and manage a separate file is to write down a long relative path or put aliases to import the file, which is not a very good developer experience.

This provides a way to initialize the tailwind config without creating a separate file (libs/tailwind.js). As a result, developers can import 'twnrc' through a single line of configuration and use it immediately.

Below is speculated to be an issue caused by tailwind config not being set up properly. I think this PR change will make it easier to set up the config and make developers less bogged down.

https://github.com/jaredh159/tailwind-react-native-classnames/issues/191

[jaredh159]

i'm really intrigued by this idea. i think it is an improvement to the API, and i want to carefully consider it. i'm a little bit concerned about initialization/configuration race conditions (making sure that no usage of importing twrnc from the bare import is executed before the one-time config happens). but if i can satisfy myself that it's not a problem, i'm really open to this (or something very similar).

might be a few days before i take a detailed look at it, but wanted to at least let you know i'm interested in this and open to merging. appreciate the time you put in to this, thanks!