meta issue. This issue itself brings us to more issues than commits [3:47am]

[frankcollins3]

as can be seen, pictured therein:

// the good news is these packages are recent enough, that upon a better configured setup, should run next ➜ next-water-app git:(main) node --version 👍 v16.20.1 ➜ next-water-app git:(main) npm --version 👍 8.19.4 ➜ next-water-app git:(main)

// the bad news is that the above fact isn't doing the setup any good now. 👎 next not found upon npm i

[frankcollins3]

this could be an issue with node versions:

for now going to reconfigure next.js with a version that might correspond better to High Sierra [3:49am]

almost forgot part of problem. I followed chatGPT advice by downloading: node-v16.20.1.tar.xz 20-Jun-2023 14:11 35556440

doing so introduced matryoshka to the party: where a zip file opened up to be another file to be another zip file

[4:09am]

[frankcollins3]

attempted to addres this by creating a new next app from which to bootstrap again with ported code. [4:13am]

[frankcollins3]

👎 v16.20.1.tar.xz --> node-v16.20.1.tar.xz.cpgz --> v16.20.1.tar.xz --> node-v16.20.1.tar.xz.cpgz

[4:22am]

would rather meet tsconfig in a vscode file but kind of neat. this is: node-v16.20.1.tar.gz

it does unpack a node file with the pictured below contents within it's directory:

[4:26am]

[frankcollins3]

proposed approach to start bootstrapping next project is downversioning node &friends. [4:28am]

[frankcollins3]

from NextJS/vercel docs: "m inimum Node.js version been bumped from 12.22.0 to 14.18.0, since 12.x reached end-of-life."

iterm2 verifying that node version (v15.14.0 seemingly well above the required 14.8.0 ➜ desktop git:(master) ✗ node --version npm --v15.14.0 ➜ desktop git:(master) ✗ npm --version 7.7.6 ➜ desktop git:(master) ✗ npx create-next-app --typescript water-app Need to install the following packages: create-next-app Ok to proceed? (y) npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'create-next-app@13.4.9', npm WARN EBADENGINE required: { node: '>=16.8.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE }

iterm verifies the version as: npm WARN EBADENGINE required: { node: '>=16.8.0' }

[4:34am]

[frankcollins3]

npm WARN EBADENGINE:

https://github.com/frankcollins3/mine-nugget-ts: went to download same next library from an app I made that uses high sierra, same OS as now.

mention of 13.4.9 which is new version but no mention of13.0.3 (allegedly HiSierra compatible) npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'next@13.4.9', npm WARN EBADENGINE required: { node: '>=16.8.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE }

[4:43am]

[frankcollins3]

proposed approach: git clone mine-nugget-ts and see if downloads go well, if so, strip app to nothing, port over ready-to-deploy water-app code [4:44am]

[frankcollins3]

also bookmarking that maybe saying yes to eslint isn't a good idea npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/scope-manager@5.42.1', npm WARN EBADENGINE required: { node: '^12.22.0 || ^14.17.0 || >=16.0.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/types@5.42.1', npm WARN EBADENGINE required: { node: '^12.22.0 || ^14.17.0 || >=16.0.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/typescript-estree@5.42.1', npm WARN EBADENGINE required: { node: '^12.22.0 || ^14.17.0 || >=16.0.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@typescript-eslint/visitor-keys@5.42.1', npm WARN EBADENGINE required: { node: '^12.22.0 || ^14.17.0 || >=16.0.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'eslint@8.27.0', npm WARN EBADENGINE required: { node: '^12.22.0 || ^14.17.0 || >=16.0.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'eslint-scope@7.1.1', npm WARN EBADENGINE required: { node: '^12.22.0 || ^14.17.0 || >=16.0.0' }, npm WARN EBADENGINE current: { node: 'v15.14.0', npm: '7.7.6' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { [4:46am]

[frankcollins3]

13.0.3 here ⸨ ⸩ ⠙ reify:next: http fetch GET 200 https://registry.npmjs.org/next/-/next-13.0.3.tgz 107119ms [4:47am]

[frankcollins3]

that's working but working means: sass, react-bootstrap, typescript, next and friends all join forces [4:48am]

[frankcollins3]

can close for now I'm in VS code getting things set up with 13.0.3.