`npm i` fails due to "could not resolve" dependencies

[nickbrooks]

Hi. Just bought Theme Designer and downloaded version 8 and ran into issues.

Current set up:

• node: v18.12.1 (latest lts version)
• npm: v8.19.2

Went to `npm i` however it failed due the following dependency issues

Code: Select all

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: primereact@8.1.1
npm ERR! Found: react@16.14.0
npm ERR! node_modules/react
npm ERR!   react@"^16.13.1" from the root project
npm ERR!   peer react@"^0.14.0 || ^15.0.0 || ^16.0.0 || ^17.0.0" from mini-create-react-context@0.4.1
npm ERR!   node_modules/mini-create-react-context
npm ERR!     mini-create-react-context@"^0.4.0" from react-router@5.2.1
npm ERR!     node_modules/react-router
npm ERR!       react-router@"5.2.1" from react-router-dom@5.3.0
npm ERR!       node_modules/react-router-dom
npm ERR!         react-router-dom@"^5.2.0" from the root project
npm ERR!   4 more (react-dom, react-router, react-router-dom, react-transition-group)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^17.0.0 || ^18.0.0" from primereact@8.1.1
npm ERR! node_modules/primereact
npm ERR!   primereact@"^8.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@18.2.0
npm ERR! node_modules/react
npm ERR!   peer react@"^17.0.0 || ^18.0.0" from primereact@8.1.1
npm ERR!   node_modules/primereact
npm ERR!     primereact@"^8.1.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

I continued with `npm i --legacy-peer-deps` and it installed the packages. However when I went to run it with `npm start` I get (presumably due to node v18):

Code: Select all

Starting the development server...

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/primereact-designer/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/primereact-designer/node_modules/webpack/lib/NormalModule.js:417:16)
    at handleParseError (/primereact-designer/node_modules/webpack/lib/NormalModule.js:471:10)
    at /primereact-designer/node_modules/webpack/lib/NormalModule.js:503:5
    at /primereact-designer/node_modules/webpack/lib/NormalModule.js:358:12
    at /primereact-designer/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/primereact-designer/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/primereact-designer/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
/primereact-designer/node_modules/react-scripts/scripts/start.js:19
  throw err;
  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/primereact-designer/node_modules/webpack/lib/util/createHash.js:135:53)
    at NormalModule._initBuildHash (/primereact-designer/node_modules/webpack/lib/NormalModule.js:417:16)
    at /primereact-designer/node_modules/webpack/lib/NormalModule.js:452:10
    at /primereact-designer/node_modules/webpack/lib/NormalModule.js:323:13
    at /primereact-designer/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /primereact-designer/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at context.callback (/primereact-designer/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at /primereact-designer/node_modules/babel-loader/lib/index.js:59:103 {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.12.1

I did test this out with node v16.18.1 and `npm start` did work however that was only after installing with `npm i --legacy-peer-deps`.

I also note that a lot of the dependencies are out of date (especially prime packages, react and react-script):

Code: Select all

computer primereact-designer % npm outdated
Package                 Current   Wanted  Latest  Location                             Depended by
axios                    0.19.2   0.19.2   1.2.0  node_modules/axios                   primereact-designer
chart.js                  2.7.3    2.7.3   4.0.1  node_modules/chart.js                primereact-designer
primeflex                 3.2.1    3.3.0   3.3.0  node_modules/primeflex               primereact-designer
primeicons                5.0.0    5.0.0   6.0.1  node_modules/primeicons              primereact-designer
primereact                8.1.1    8.7.2   8.7.2  node_modules/primereact              primereact-designer
prismjs                   1.9.0    1.9.0  1.29.0  node_modules/prismjs                 primereact-designer
react                   16.14.0  16.14.0  18.2.0  node_modules/react                   primereact-designer
react-dom               16.14.0  16.14.0  18.2.0  node_modules/react-dom               primereact-designer
react-router-dom          5.3.0    5.3.4   6.4.3  node_modules/react-router-dom        primereact-designer
react-scripts             3.4.1    3.4.1   5.0.1  node_modules/react-scripts           primereact-designer
react-transition-group    4.4.2    4.4.5   4.4.5  node_modules/react-transition-group  primereact-designer
sass                     1.43.4   1.43.4  1.56.1  node_modules/sass                    primereact-designer

I've worked around all of the above by updating most of the packages to the latest and it seems to work fine for now (on node v18.12.1).

I know this is only $490 usd, however given the great experience we've had with prime-react, the experience so far with the theme designer was an unpleasant surprise.

[mert.sincan]

Sorry for the delayed response! We'll check and get back to you.

[nickbrooks]

Hi!

Is there any update on this?

Thanks,
Nicholas

[mert.sincan]

So sorry for the delayed response! We're checking now and will make a new release asap. Sorry again!

[yann-J]

hello ,

i try today but he problem is still there.
What is the way to have a designer that works?

have a nice day .

[mert.sincan]

Interesting! I tried it now. It works fine for me.

Those that are outdated are because they released new versions with the project itself or after we released it. It will not create a problem for you in generating themes.