Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial feedback from running the app-nextjs template #301

Open
adriatic opened this issue Jan 18, 2023 · 3 comments
Open

Initial feedback from running the app-nextjs template #301

adriatic opened this issue Jan 18, 2023 · 3 comments

Comments

@adriatic
Copy link

adriatic commented Jan 18, 2023

Issue 1 - few compilation error

image

To get the clean display of _app.tsx I had to run npm i --save-dev --force @types/node (note that running without the --force flag, the installation of types failed as shown below

npm i --save-dev @types/node
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: app-nextjs@0.1.0
npm ERR! Found: react@18.2.0
npm ERR! node_modules/react
npm ERR!   react@"18.2.0" from app-nextjs@0.1.0
npm ERR!   packages/app-nextjs
npm ERR!     app-nextjs@0.1.0
npm ERR!     node_modules/app-nextjs
npm ERR!       workspace packages/app-nextjs from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.11.0 || ^17.0.0" from swr@0.4.2
npm ERR! node_modules/swr
npm ERR!   swr@"^0.4.0" from app-nextjs@0.1.0
npm ERR!   packages/app-nextjs
npm ERR!     app-nextjs@0.1.0
npm ERR!     node_modules/app-nextjs
npm ERR!       workspace packages/app-nextjs 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 reso

At those point the this mini-app behaves fine

image

@adriatic
Copy link
Author

Added later: this time I tried to use the project https://goldstack.party/projects/6652427a-99aa-4b7d-8216-04d8b8c966b5/packages/96ae4b71-0b27-4f78-b32b-b40804fcd334/download (NextJS + bootstrap) and the step yarn (same as yarm install) failed with

  rm -f Release/sass.a && ./gyp-mac-tool filter-libtool libtool  -static -o Release/sass.a Release/obj.target/libsass/src/libsass/src/ast.o Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o Release/obj.target/libsass/src/libsass/src/backtrace.o Release/obj.target/libsass/src/libsass/src/base64vlq.o Release/obj.target/libsass/src/libsass/src/bind.o Release/obj.target/libsass/src/libsass/src/cencode.o Release/obj.target/libsass/src/libsass/src/check_nesting.o Release/obj.target/libsass/src/libsass/src/color_maps.o Release/obj.target/libsass/src/libsass/src/constants.o Release/obj.target/libsass/src/libsass/src/context.o Release/obj.target/libsass/src/libsass/src/cssize.o Release/obj.target/libsass/src/libsass/src/emitter.o Release/obj.target/libsass/src/libsass/src/environment.o Release/obj.target/libsass/src/libsass/src/error_handling.o Release/obj.target/libsass/src/libsass/src/eval.o Release/obj.target/libsass/src/libsass/src/expand.o Release/obj.target/libsass/src/libsass/src/extend.o Release/obj.target/libsass/src/libsass/src/file.o Release/obj.target/libsass/src/libsass/src/functions.o Release/obj.target/libsass/src/libsass/src/inspect.o Release/obj.target/libsass/src/libsass/src/json.o Release/obj.target/libsass/src/libsass/src/lexer.o Release/obj.target/libsass/src/libsass/src/listize.o Release/obj.target/libsass/src/libsass/src/memory/SharedPtr.o Release/obj.target/libsass/src/libsass/src/node.o Release/obj.target/libsass/src/libsass/src/operators.o Release/obj.target/libsass/src/libsass/src/output.o Release/obj.target/libsass/src/libsass/src/parser.o Release/obj.target/libsass/src/libsass/src/plugins.o Release/obj.target/libsass/src/libsass/src/position.o Release/obj.target/libsass/src/libsass/src/prelexer.o Release/obj.target/libsass/src/libsass/src/remove_placeholders.o Release/obj.target/libsass/src/libsass/src/sass.o Release/obj.target/libsass/src/libsass/src/sass2scss.o Release/obj.target/libsass/src/libsass/src/sass_context.o Release/obj.target/libsass/src/libsass/src/sass_functions.o Release/obj.target/libsass/src/libsass/src/sass_util.o Release/obj.target/libsass/src/libsass/src/sass_values.o Release/obj.target/libsass/src/libsass/src/source_map.o Release/obj.target/libsass/src/libsass/src/subset_map.o Release/obj.target/libsass/src/libsass/src/to_c.o Release/obj.target/libsass/src/libsass/src/to_value.o Release/obj.target/libsass/src/libsass/src/units.o Release/obj.target/libsass/src/libsass/src/utf8_string.o Release/obj.target/libsass/src/libsass/src/util.o Release/obj.target/libsass/src/libsass/src/values.o
env: python: No such file or directory
make: *** [Release/sass.a] Error 127
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/nik/dev/learning/nextjs/nextjs-bootstrap/.yarn/unplugged/node-gyp-npm-7.1.2-002c5798eb/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Darwin 22.3.0
gyp ERR! command "/usr/local/bin/node" "/Users/nik/dev/learning/nextjs/nextjs-bootstrap/.yarn/unplugged/node-gyp-npm-7.1.2-002c5798eb/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /Users/nik/dev/learning/nextjs/nextjs-bootstrap/.yarn/unplugged/node-sass-npm-7.0.0-142deb23e8/node_modules/node-sass
gyp ERR! node -v v18.14.0
gyp ERR! node-gyp -v v7.1.2
gyp ERR! not ok 
Build failed with error code: 1

Running yarn install for the second time resulted with success

@mxro
Copy link
Collaborator

mxro commented Feb 25, 2023

Thank you for raising the issues! For the second project, I think this could be related to: nodejs/node-gyp#809

For the first issues reported, did you encounter this in the second project as well?

@adriatic
Copy link
Author

nodejs/node-gyp#809 is too scary for me to parse (I have years of node-gyp related issues and none of them I really understood 😢.

For the first issues reported, did you encounter this in the second project as well?

No, I did not - it was a consequence of something very weird in my node installation. Not knowing any better, I mixed script based installations with brew based updates until I realized that many people advise not to use brew for anything node related.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants