ohduran / cookiecutter-react-django Goto Github PK

Is your feature request related to a problem? Please describe.
Add the ability to use styled components by default

Describe the solution you'd like
npm install --save styled-components inside the react container so that package.json reflects the changes

Multi-stage builds allow for optimising Dockerfiles while keeping them easy to read and maintain. Check out Docker docs on it.

See also this on the specific case of create-react-app.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Update dependency jest-environment-jsdom-sixteen to v2
• Update dependency react-scripts to v5
• Update dependency typescript to v5
• Update github/codeql-action action to v3
• Update react monorepo to v18 (major) (react, react-dom)
• Update testing-library monorepo (major) (@testing-library/jest-dom, @testing-library/react, @testing-library/user-event)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency axios to v0.28.0 [SECURITY]
• Update dependency eslint-plugin-flowtype to v5.10.0
• Update dependency typescript to v4.9.5
• Update testing-library monorepo (@testing-library/jest-dom, @testing-library/user-event)
• Update actions/checkout action to v4
• Update dependency Sphinx to v7
• Update dependency dotenv to v16
• Update dependency eslint-config-react-app to v7
• Update dependency eslint-plugin-flowtype to v8
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Have a look at the Sphinx tutorial on how to start the documentation for this project.

Webhooks have been created for this project, so the scope for this task is creating the actual files.

Instead of relying on Heroku, why not setting up something as simple that leverages the Docker configuration and reduce costs?

Incorporate CapRover as an option (https://caprover.com/) for app deployment.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: renovate.json
Error type: Invalid JSON (parsing failed)
Message: Syntax error: expecting String near ], assig

Check out this PR from @renovate-bot . Tests are failing in the new version of @testing-library/react!

A couple of things in the way the app is tested should change so that the tests can pass using the newest version of @testing-library/react

I'm sick of Travis CI blocking the whole operation because I ran out of their credits. Let's move to Github Actions and make this project self-adjusting again.

https://rasulkireev.com/managing-django-with-poetry/

Although Travis is already set up, it's running only on the version of Python, Node, Django and React defined by the Dockerfiles. As a developer, I want, as many other projects do—such as Django Rest Framework— to run the tests on more than one combination of Python, Node, Django and React versions.

It would be a good idea to start by reading Tox documentation.

I get the following error when I do docker-compose up --build with no image preloaded on Docker.

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './plugin-bugfixes' is not defined by "exports" in /app/node_modules/@babel/compat-data/package.json

Describe the bug
I'm trying to get set up with this awesome cookiecutter on MacOS on an M1 MacBook. The frontend fails to start.

To Reproduce
Steps to reproduce the behavior:

1. Run the cookiecutter
2. Run $ docker-compose up

Expected behavior
Both containers start.

Screenshots
Here's the terminal output from after I run docker-compose up

Starting project_name_django_1 ... done
Starting project_name_react_1  ... done
Attaching to project_name_django_1, project_name_react_1
django_1  | Watching for file changes with StatReloader
django_1  | Performing system checks...
django_1  | 
django_1  | System check identified no issues (0 silenced).
django_1  | August 20, 2021 - 15:29:12
django_1  | Django version 4.0, using settings 'backend.settings.development'
django_1  | Starting development server at http://0.0.0.0:8000/
django_1  | Quit the server with CONTROL-C.
react_1   | 
react_1   | > [email protected] start
react_1   | > react-scripts start
react_1   | 
react_1   | ℹ ｢wds｣: Project is running at http://172.18.0.3/
react_1   | ℹ ｢wds｣: webpack output is served from 
react_1   | ℹ ｢wds｣: Content not from webpack is served from /app/public
react_1   | ℹ ｢wds｣: 404s will fallback to /
react_1   | Starting the development server...
react_1   | 
project_name_react_1 exited with code 0

Desktop (please complete the following information):

• OS: MacOS
• Version 11.5.2
• Apple M1

Additional context
npm i npm start works just fine, but can't connect to the backend because the settings seem to be expecting docker.

Is there anything that we might find useful from this link: https://mattsegal.dev/django-react.html

Make sure that the dependencies in React are up to date, and no unnecessary libraries are installed.

The following warnings are shown when doing docker-compose build --no-cache react:

npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1

npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142

npm WARN deprecated [email protected]: use String.prototype.padStart()

npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

npm WARN [email protected] requires a peer of [email protected] but none is installed. You must install peer dependencies yourself.

npm WARN [email protected] requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.

Describe the bug
Everytime I try to run tests either from inside the django container or from outside (invoking docker-compose command) I always get an error

To Reproduce
Steps to reproduce the behavior:

1. Run test using docker-compose run --rm django pytest
2. See error

Expected behavior
Expected behavior is that that the tests run and a test report shows up on cli

Screenshots

Desktop (please complete the following information):

• OS: Ventura 13.6.6

Additional context
Add any other context about the problem here.

Description
Django now allows for async functionalities, and the project is unfortunately in need for configuration to do just that.

Possible solution
A good starting point is this article from @suda.

Alternatives
There are two options that might be on the table:
a) Just move into this configuration by default, and drop support for Django 2 and lower.
b) Cookiecutter allows for the user to decide whether to use it or not in the cookiecutter.json

Mi own preferences lean to the a) side given that a cookiecutter allows for jumpstart a new project from scratch, and it should look into the future, and not to the past.