The issue tracker is only for technical support, bug reports and enhancement suggestions. If you have a question, please ask it in the Discord server instead of opening an issue.
If you wish to contribute to the MonitoRSS-Web, feel free to fork the repository and submit a pull request. ESLint and StandardJS are used to enforce a consistent coding style, so having that set up in your editor of choice is a great boon to your development process.
All development happens on dev branches.
- Fork & clone this repo
- Create a new branch from the dev branch
- Code!
- Run
npm run eslint
to run ESLint and automatically fix problems in coding style - Use
npm link
this repo from the clone repo to test changes - Push your work to your fork and submit a pull request (before that you may need to merge the latest from upstream)
npm install
in src/clientnpm start
(to access the control panel, you must login via the server, then go back to the create-react-app's dev server on port 3000 so the session is available)- Code!
npm run build
(build files are uploaded for the user)- Run
npm run eslint
to run ESLint and automatically fix problems in coding style - Push your work to your fork and submit a pull request (before that you may need to merge the latest from upstream)
If you use an outdated version of npm, then you may run into a lock file conflict. More info here and here.
How do I know which version of npm comes with which version of Node.js ?