This is example how you can integrate a Tailwind technologie in your React project.
To install and run this project follow these steps:
- Clone this repository
- Go in
you-directory/tailwind-gallery npm install- Create
.envfile and paste there your Pixabay API Key (REACT_APP_PIXABAY_API_KEY).
You can get it here npm start
The complete list of npm-scripts is avalibale below.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
It will also create a main.css with compiled tailwind styles in the assets folder.
See also watch:css script.
The page will reload if you make edits.
You will also see any lint errors in the console.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
Also it compiles a tailwind.scss. See build:css script.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Builds all of tailwind.scss styles to src/assets/main.css.
Also builds a map file for debug puproses.
As in watch:css it builds all of tailwind.scss styles to src/assets/main.css.
But builds no map files. Futher optimizations can be added with plugins.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
In this project I use some technologies:
- Create React App - documentation.
- Tailwind - documentation
- PostCSS - documentation
- React - documentation.
Sierikov Artem – twitter
Distributed under the MIT License. See LICENSE.md for more information.
- Read Code of Conduct.
- Fork it (https://github.com/sierikov/tailwind-gallery/fork)
- Create your feature branch (
git checkout -b feature/fooBar) - Commit your changes (
git commit -am 'Add some fooBar') - Push to the branch (
git push origin feature/fooBar) - Create a new Pull Request