Unable to successfully run "npm install" in Manjaro Linux. #167
Comments
|
Oops, I pressed enter too fast. I cloned the repo, then ran full outputI get the same errors with Any ideas? Looking forward to trying this. :) |
|
Same for MacOS Catalina 10.15.5 :( |
|
Fixed by changing Node.JS Version to 12.16.2 |
|
This is probably more a Meteor issue than a Vulcan issue, we updated to 1.10 just recently on the devel branch. |
|
Hi, as Joe @trusktr I would like to test this [coming from old meteor days ;-) ] Unfortunaley it doesnt work as described. I tested with node v10.20.0 and v12.16.3 as well as with master and devel branch from this repo and meteor 1.8. Neither master or devel may be able to be updated to meteor 1.10 via meteor update. With devel branch I can't even run npm install With master branch npm install will run when using node v10.20.0 but when starting via npm start, I get this error when opening localhost:3000 result npm installnpm WARN jss-camel-case@6.1.0 requires a peer of jss@^9.7.0 but none is installed. You must install peer dependencies yourself. npm WARN jss-default-unit@8.0.2 requires a peer of jss@^9.4.0 but none is installed. You must install peer dependencies yourself. npm WARN jss-global@3.0.0 requires a peer of jss@^9.0.0 but none is installed. You must install peer dependencies yourself. npm WARN jss-nested@6.0.1 requires a peer of jss@^9.0.0 but none is installed. You must install peer dependencies yourself. npm WARN jss-props-sort@6.0.0 requires a peer of jss@^9.0.0 but none is installed. You must install peer dependencies yourself. npm WARN jss-vendor-prefixer@7.0.0 requires a peer of jss@^9.0.0 but none is installed. You must install peer dependencies yourself. npm WARN react-no-ssr@1.1.0 requires a peer of react@^0.14.0 || ^15.0.0 but none is installed. You must install peer dependencies yourself. npm WARN react-router-scroll@0.4.4 requires a peer of react-router@^2.3.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself. audited 34051 packages in 11.662s 16 packages are looking for funding run `npm fund` for details found 799 vulnerabilities (592 low, 9 moderate, 198 high) run `npm audit fix` to fix them, or `npm audit` for details result from console on access=> Started your app. => App running at: http://localhost:3000/ I20200429-03:27:36.603(2)? GraphQL schema saved to /Users/xy/Workspace/Meteor-Vulcan/hello-world/schema.graphql W20200429-03:27:49.991(2)? (STDERR) Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object. W20200429-03:27:49.991(2)? (STDERR) in HeadTags W20200429-03:27:49.991(2)? (STDERR) in div W20200429-03:27:49.991(2)? (STDERR) in Context.Provider W20200429-03:27:49.991(2)? (STDERR) in IntlProvider W20200429-03:27:49.992(2)? (STDERR) in App W20200429-03:27:49.992(2)? (STDERR) in Context.Consumer W20200429-03:27:49.992(2)? (STDERR) in withRouter(App) W20200429-03:27:49.992(2)? (STDERR) in withCookies(Component) W20200429-03:27:49.992(2)? (STDERR) in Context.Consumer W20200429-03:27:49.993(2)? (STDERR) in ApolloConsumer W20200429-03:27:49.993(2)? (STDERR) in withApollo(withCookies(Component)) W20200429-03:27:49.993(2)? (STDERR) in withUpdateUser W20200429-03:27:49.993(2)? (STDERR) in withSiteData W20200429-03:27:49.993(2)? (STDERR) in withCurrentUser W20200429-03:27:49.993(2)? (STDERR) in CookiesProvider W20200429-03:27:49.993(2)? (STDERR) in Context.Provider W20200429-03:27:49.993(2)? (STDERR) in Router W20200429-03:27:49.994(2)? (STDERR) in StaticRouter W20200429-03:27:49.994(2)? (STDERR) in Context.Provider W20200429-03:27:49.994(2)? (STDERR) in Context.Consumer W20200429-03:27:49.994(2)? (STDERR) in ApolloProvider W20200429-03:27:49.994(2)? (STDERR) in AppGenerator W20200429-03:27:49.994(2)? (STDERR) in Context.Provider W20200429-03:27:50.148(2)? (STDERR) Error while server-rendering. date: Wed Apr 29 2020 03:27:50 GMT+0200 (CEST) url: [object Object] W20200429-03:27:50.149(2)? (STDERR) Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. W20200429-03:27:50.149(2)? (STDERR) at ReactDOMServerRenderer.render (/Users/xy/Workspace/Meteor-Vulcan/hello-world/node_modules/react-dom/cjs/react-dom-server.node.development.js:4006:17) W20200429-03:27:50.149(2)? (STDERR) at ReactDOMServerRenderer.read (/Users/xy/Workspace/Meteor-Vulcan/hello-world/node_modules/react-dom/cjs/react-dom-server.node.development.js:3536:29) W20200429-03:27:50.150(2)? (STDERR) at renderToStaticMarkup (/Users/xy/Workspace/Meteor-Vulcan/hello-world/node_modules/react-dom/cjs/react-dom-server.node.development.js:4261:27) W20200429-03:27:50.150(2)? (STDERR) at process (/Users/xy/Workspace/Meteor-Vulcan/hello-world/node_modules/@apollo/react-ssr/lib/react-ssr.cjs.js:38:16) W20200429-03:27:50.150(2)? (STDERR) at /Users/xy/Workspace/Meteor/packages/promise/.0.11.2.7ew9go.l2l79++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/fiber_pool.js:43:40 W20200429-03:27:50.150(2)? (STDERR) => awaited here: W20200429-03:27:50.150(2)? (STDERR) at Function.Promise.await (/Users/xy/Workspace/Meteor/packages/promise/.0.11.2.7ew9go.l2l79++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/promise_server.js:56:12) W20200429-03:27:50.150(2)? (STDERR) at Promise.asyncApply (packages/vulcan:lib/lib/server/apollo-ssr/renderPage.js:61:7) W20200429-03:27:50.150(2)? (STDERR) at /Users/xy/Workspace/Meteor/packages/promise/.0.11.2.7ew9go.l2l79++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/fiber_pool.js:43:40 It would be great to get some answers to get this running Thanks |
|
@TomFreudenberg can you please check your version of react-helmet? It should be version 6 I've checked the package.json of the Vulcan starter and it should be ok. This error is probably thrown by this line: https://github.com/VulcanJS/Vulcan/blob/devel/packages/vulcan-core/lib/modules/components/HeadTags.jsx#L3 You should check Starter on "master" and Vulcan on "devel" (sorry for the difference in branches, we are preparing a release very soon, I've merged the react-helmet update on the starter master instead of devel). |
|
Hi @eric-burel yes, it is version 6
Does it mean I should use the https://docs.vulcanjs.org/#Two-Repo-Install-Optional procedure with master and devel branches as you mentioned? |
|
Yeah if the normal install is broken that's better, sorry for this normally the master branch of the starter is supposed to work with the currently published version. Will be fixed soon. |
|
Hi @eric-burel can't make it in any way: That's the used code basecd /tmp
mkdir testVulcan
cd testVulcan
git clone -b devel https://github.com/VulcanJS/Vulcan
git clone -b master https://github.com/VulcanJS/Vulcan-Starter.git
cd Vulcan-Starter
mv sample_settings.json settings.jsonThat's my used toolsnvm use --lts=Erbium
node --version
# response: v12.16.3
cd /tmp/testVulcan
meteor --version
# reponse: Meteor 1.10.2
cd /tmp/testVulcan/Vulcan
meteor --version
# response: Meteor 1.10.2
cd /tmp/testVulcan/Vulcan-Starter
meteor --version
# response: Meteor 1.8.1Try 1cd /tmp/testVulcan/Vulcan-Starter
npm installRESULT 1This at least failed on build bcrypt npm ERR! Failed at the bcrypt@3.0.3 install script. Try 2# use node 10
nvm use --lts=Dubnium
cd /tmp/testVulcan/Vulcan-Starter
npm install
METEOR_PACKAGE_DIRS="/tmp/testVulcan/Vulcan/packages" meteor --port 3000 --settings settings.jsonRESULT 2This will build but failed running the app => Started proxy. => Meteor 1.10.2 is available. Update this project with 'meteor update'. => Errors prevented startup: While selecting package versions: error: Conflict: Constraint apollo@3.1.0 is not satisfied by apollo 0.0.1. Constraints on package "apollo": * apollo@3.1.0 <- vulcan:lib 1.14.1 <- vulcan:core 1.14.1 => Your application has errors. Waiting for file change. Selecting package versions - Try 3 to XYZWhatever combination of node and meteor - always fail on build node-gyp bcrypt. It also makes no difference if using METEOR_PACKAGE_DIRS="/tmp/testVulcan/Vulcan/packages" meteor npm installnpm installOff-topic: I remember a number of issues with bcrypt when I worked on the meteor-universal forks :-( |
|
You mentioned Vulcan 2.0 based on next.js to me. Is there already a starter or kind of documentation to go on with that? Maybe better than to spend effort into other. |
|
Regarding the Apollo version constraint come on Slack, you are not the only one to have this issue. Basically it's Meteor going nuts during update for no reason, but some users have found solutions for this. Sadly no for Next version, we are currently investigating Next possibilities and limitations thoroughly before doing anything. |
|
From @kevinashworth
|
|
Hi @eric-burel after a day of trying different releases - constraints etc. - result: WON'T WORK :-( I have managed to install and get VulcanJS from devel build and running. That is now using meteor 1.10.2 But the starter based on meteor 1.8.1 is a mess in case of constraint conflicts. Neither combination were successfull and could get started. I guess it would be the right way to upgrade the starter also to meteor 1.10.x. Do you have some tips how to proceed with that upgrade? Where to best find documentation for the updated APIs? Thanks for some guidiance P.S.: If you prefer I may come in contact via Slack. |
|
Maybe my question was a bit unclear - is there a chance to start a VulcanJS project without the Starter project? |
|
YIHAAA Find a way to get the Steps to reproduce:nvm use --lts=Erbium
cd /your-project-path
git clone -b devel https://github.com/VulcanJS/Vulcan
# Open and edit the package.json
vi package.json
# find bcrypt and change release to 3.0.8
# find node-sass and change release to 4.13.1
# Open and edit the .meteor/packages
vi .meteor/packages
# remove release info @1.x.x from accounts-password
# install npms
meteor npm install bcrypt
meteor npm install
meteor npm install @babel/runtime@latest
meteor npm install body-parser-graphql
# update to latest meteor (currently 1.10.2)
meteor update
meteor update --all-packagesNow you should be able to run Get the examplenvm use --lts=Erbium
cd /your-project-path
git clone -b master https://github.com/VulcanJS/Vulcan-Starter
# cd into VULCAN folder
cd Vulcan
# copy example package from Starter
cp -pr ../Vulcan-Starter/packages/example-simple packages
# Open and edit .meteor/packages
vi .meteor/packages
# add line: example-simple
# at last line
# get settings sample from Starter
cp -p ../Vulcan-Starter/sample_settings.json settings.json
# FINAL run meteor
meteor --port 3000 --settings settings.jsonNow you should get the example simple app in your browser. TADAAAA @eric-burel - I will create a fork and send you a pull request |
This was referenced Apr 30, 2020
|
Until the PRs are accepted you may try: nvm use --lts=Erbium
cd /your-working-space
git clone -b devel https://github.com/TomFreudenberg/Vulcan.git
git clone -b master https://github.com/TomFreudenberg/Vulcan-Starter.git
cd Vulcan-Starter
cp sample-settings.json settings.json
METEOR_PACKAGE_DIRS="../Vulcan/packages" meteor npm install
METEOR_PACKAGE_DIRS="../Vulcan/packages" meteor --port 3000 --settings settings.json |
|
@trusktr Joe - wondering if that fixes the issue on your side too? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: