This version has been deprecated in accordance with the hapi support policy (hapi.im/support)...

OS: MX linux 19 , i have been tring to install expo ,tried many things avaiblable on the internet but still getting the erorr …Help needed…Thanks in advane

sudo npm install -g --unsafe-perm expo-cli

npm WARN deprecated joi@14.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm ERR! Unexpected end of JSON input while parsing near ‘…pendencies":{"@jimp/c’

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-21T14_45_33_503Z-debug.log

Hi.

The Warning you are quoting is just a warning and can be ignored. The Error looks more serious. Why do you need the --unsafe-perm option?

What is the full error message?

If you post it here, use the “</>” button to allow it to keep its formatting.

--unsafe-perm was suggested as solution in git but not working in my case.
i tried without the --unsafe-perm the error is still remain same.

the file is too big , and its body(expo forum reply) has some limit…showing u only the error part .Hope it will help you to get the issue…

1726 http fetch GET 304 https://registry.npmjs.org/@jimp%2fplugin-normalize 183ms (from cache)
1727 silly fetchPackageMetaData error for @jimp/plugin-normalize@^0.9.3 Unexpected end of JSON input while parsing near '...sodfCxKMdYsTQjnjDxN82'
1728 http fetch GET 304 https://registry.npmjs.org/@jimp%2fplugin-print 178ms (from cache)
1729 silly pacote range manifest for @jimp/plugin-print@^0.9.3 fetched in 180ms
1730 silly resolveWithNewModule @jimp/plugin-print@0.9.3 checking installable status
1731 http fetch GET 304 https://registry.npmjs.org/@jimp%2fplugin-rotate 195ms (from cache)
1732 silly pacote range manifest for @jimp/plugin-rotate@^0.9.3 fetched in 198ms
1733 silly resolveWithNewModule @jimp/plugin-rotate@0.9.3 checking installable status
1734 http fetch GET 304 https://registry.npmjs.org/@jimp%2fplugin-scale 528ms (from cache)
1735 silly pacote range manifest for @jimp/plugin-scale@^0.9.3 fetched in 530ms
1736 silly resolveWithNewModule @jimp/plugin-scale@0.9.3 checking installable status
1737 http fetch GET 304 https://registry.npmjs.org/timm 849ms (from cache)
1738 silly pacote range manifest for timm@^1.6.1 fetched in 850ms
1739 silly resolveWithNewModule timm@1.6.2 checking installable status
1740 http fetch GET 304 https://registry.npmjs.org/@jimp%2fplugin-resize 871ms (from cache)
1741 silly pacote range manifest for @jimp/plugin-resize@^0.9.3 fetched in 874ms
1742 silly resolveWithNewModule @jimp/plugin-resize@0.9.3 checking installable status
1743 timing stage:rollbackFailedOptional Completed in 1ms
1744 timing stage:runTopLevelLifecycles Completed in 61584ms
1745 verbose stack SyntaxError: Unexpected end of JSON input while parsing near '...\n"}},"0.8.2-canary.7'
1745 verbose stack     at JSON.parse (<anonymous>)
1745 verbose stack     at parseJson (/usr/lib/node_modules/npm/node_modules/json-parse-better-errors/index.js:7:17)
1745 verbose stack     at /usr/lib/node_modules/npm/node_modules/node-fetch-npm/src/body.js:96:50
1745 verbose stack     at runMicrotasks (<anonymous>)
1745 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:93:5)
1746 verbose cwd /home/Rajendra
1747 verbose Linux 4.19.0-6-amd64
1748 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "-g" "expo-cli"
1749 verbose node v12.14.0
1750 verbose npm  v6.13.4
1751 error Unexpected end of JSON input while parsing near '...\n"}},"0.8.2-canary.7'
1752 verbose exit [ 1, true ]

thanks in advance

Can you try running:

npm cache clean --force

and then try again to install expo-cli? Strangely it seems as if the JSON it is complaining about in your earlier comment is different to that in your latest comment. It looks a bit like the packages are corrupt maybe as a result of not downloading fully?

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.