No description provided.
I decided to give this a shot when integrating into an existing project and came across path referencing issues, specifically for npm based commands that are run via the `subprocess.Popen` commands (apologies if I've got the terminology wrong here). I've got the path to my npm set up correctly, can run the `npm exec generate_client_configuration` globally from the terminal and can see the path when printing out the PATH env variable before the command. Specifiying the full path to `npm` in those commands works and I wasn't sure where to next in terms of fault finding. A potential solution I've seen is in the [django-tailwind ](https://django-tailwind.readthedocs.io/en/latest/installation.html) app, where the path to `npm` can be set within the settings file to overcome this issue. A quick look through the source shows `reactivated\app.py` and `reactivated\__init__.py` containing references to `npm`, I'd be happy to create a PR but I'm still quite new to the git side of house so bear with me on that front haha
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by grant-oscillolabs and has received 3 comments.