Error while trying to create a project

[ahanabhattchrya]

Hi, I’ve been trying to create a project for a while now using this repo but I keep getting an error that prevents me to do so. For reference this is what the error looks like - ERROR: Stopping generation because post_gen_project hook script didn't exit successfully Hook script failed (exit status: 1)
I was wondering if there is a solution to this issue yet and/or if there is anything I should change locally to fix it? (If it helps, I’m trying to run it on a Terminal/MacOS)

[marcjulianschwarz]

I am getting the same error message (running macOS).

@ahanabhattchrya, did you get it working?

[ridhwaanm]

same error Linux, Node.js v17.9

[dmeinrath]

#108

this project breaks now for anyone using the current Node LTS version 18

i'm trying to help a client make a build pipeline that converts their react components into there dash application, so I'm trying to figure out how to fix this;
my current understanding:
the Webpack and Webpack CLI versions needs to be updated to 5.0.0 that they support OpenSSL3 in the current Node. However, doing this breaks another dependency called webpack-serve which looks pretty much abandoned

does anyone else more familiar with webpack or react or dash know what webpack-serve actually does here?

for reference: https://github.com/shellscape/webpack-serve

[Elbarto]

Hey,

As I was facing the same issue I tried to find a temporary fix. One way to handle the error is to set the environ variable :
NODE_OPTIONS=--openssl-legacy-provider

To do that you need to edit the hook/post_gen_project.py file

Add the following line before the execution of _execute_command('npm run build:js') at line 93:

1. Windows : _execute_command("set NODE_OPTIONS=--openssl-legacy-provider")
2. Linux : _execute_command("export NODE_OPTIONS=--openssl-legacy-provider")

Note this is a temporary fix that can lead to security issue.

[chibi-dogs]

Node LTS version 18

Just wondering, but would using an older version of Node help fix the issue?

[ridhwaanm]

It does fix the problem but exposes security issues.

…

On Mon, 30 Jan 2023, 11:39 am Basab ***@***.***> wrote: Node LTS version 18 Just wondering, but would using an older version of Node help fix the issue? — Reply to this email directly, view it on GitHub <#148 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQUW2IYJFCPD45VHKZLW2LLWU6D5XANCNFSM54GPXRCQ> . You are receiving this because you commented.Message ID: ***@***.***>

[chibi-dogs]

Okay. Here is a short update. I managed to get cookiecutter to run by using an older version of node. @ridhwaanm is right about the security issues though.
Currently using

• node version (v14.16.0)
• npm version (6.14.11)