npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

dimasa-react-php_v1

v0.1.0

Published

This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).

Downloads

3

Readme

PHP+React

Это небольшое сочитание кода php и фреймворка react.

Философия данного проекта такова: тк, React в большенстве случаев является приложением для 1 страницы, это вызывает боль у бэкендеров(меня в частности). Я решил что главное в react это сам js после компиляции, и тем самым, можно заранее написать весь неоходимый код на react, скомпилировать, и положить в папку сайта.

Основная идея, это заранее подготовить скрипты, страницы, и закинуть их в index.js с условием if(id,css,...) будет найдено, то запускается скрипт.

Способ использования.

Подготавливаем весть js, jsx коды, закидываем как обычно в index.js готовые решения как и в обычном react и компилируем.

После компиляции у нас будет папка build в которой уже будет созданна 1 страница, но нам это не надо. Самое главное это файлы в static в частности js. После компиляции, запускаем сайт, включая OpenServer или как-то иначе, главное что-бы php работал. Заходим в корень папки, и заходим в index.php после чего, просто тыкаем компилировать(на самом деле это просто копирование бех хеш ключа). И все, у вас в вашей папке будет файлы js и css после компиляции react.

Необходимые изменения.

В корне есть package.json это основные конфигурации, которые можно отредактировать. Заходим в этот файл, и ищем 4 строки:

Корень-Термин означающий главную папку

1-homepage: путь к папке build из корня домена пример /react_app/my-test-app/build 2-base-js: путь к статике js если вы не редактировали путь записи, то оставляйте как есть 3-base-css: путь к статике css если вы не редактировали путь записи, то оставляйте как есть 4-path_yours_site: путь из текущего корня куда будут копироваться js и css вот php_react/Site

Getting Started with Create React App

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

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.

npm run eject

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.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify