Hi,
My previous windows 8 computer is broken so I got a new computer with windows 10.
Now I can not run my meteor project on windows 10.
I have installed meteor with Chocolatey, then:
#1 meteor npm install
#2 meteor --settings=settings-dev.json
What am I doing wrong?
My computer crashes every time, I have to restart the computer.
It never finishes to download meteor packages.
Regards,
Are you getting any errors?
What steps did you follow when installing?
Did you install chocolatey and meteor in an administrator command prompt?
Did you create and run your project in a non-administrator command prompt?
Hi,
Are you getting any errors?
No, my computer crashes every time, I have to restart the computer.
I am not able to see if there are errors.
What steps did you follow when installing?
#1 install meteor with chocolatey
#2 meteor npm install
#3 meteor --settings=settings-dev.json
Did you install chocolatey and meteor in an administrator command prompt?
I did, I install them with Administrator PowerShell which comes with windows 10 by default.
Did you create and run your project in a non-administrator command prompt?
I have tried both: command prompt and PowerShell.
I tried to create a new project and I could not, at least my computer did not crash.
The output is the following from the Windows PowerShell:
PS D:\repos> meteor create simple-todos
C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\met
eor-promise\promise_server.js:218
throw error;
^
Error: Error: Could not install npm dependencies for test-packages: Command failed: C:\windows\system32\cmd.exe /c C:\Us
ers\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\bin\npm.cmd install --pro
duction=false
npm ERR! write after end
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USUARIO\AppData\Roaming\npm-cache\_logs\2018-07-06T04_22_56_631Z-debug.log
npm ERR! write after end
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USUARIO\AppData\Roaming\npm-cache\_logs\2018-07-06T04_22_56_631Z-debug.log
at Object.error (C:\tools\utils\buildmessage.js:430:11)
at C:\tools\cli\default-npm-deps.js:36:20
at C:\tools\utils\buildmessage.js:334:18
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:333:36
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at Object.install (C:\tools\cli\default-npm-deps.js:27:27)
at Command.func (C:\tools\cli\commands.js:807:36)
at C:\tools\cli\main.js:1531:15
PS D:\repos>
I tried to create a new project and I could not, at least my computer did not crash.
The output is the following from the regular command (cmd):
D:\repos>meteor create hello-world
C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
throw error;
^
Error: Error: Could not install npm dependencies for test-packages: Command failed: C:\windows\system32\cmd.exe /c C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\bin\npm.cmd install --production=false
npm ERR! write after end
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USUARIO\AppData\Roaming\npm-cache\_logs\2018-07-06T04_32_26_869Z-debug.log
npm ERR! write after end
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USUARIO\AppData\Roaming\npm-cache\_logs\2018-07-06T04_32_26_869Z-debug.log
at Object.error (C:\tools\utils\buildmessage.js:430:11)
at C:\tools\cli\default-npm-deps.js:36:20
at C:\tools\utils\buildmessage.js:334:18
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:333:36
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at Object.install (C:\tools\cli\default-npm-deps.js:27:27)
at Command.func (C:\tools\cli\commands.js:807:36)
at C:\tools\cli\main.js:1531:15
D:\repos>meteor create simple-todos
If your entire computer crashes when trying to run Meteor, that sounds like a serious hardware issue
You mention using meteor --settings=settings-dev.json but none of the official new project skeletons contain settings. Are you using a different scaffolding tool?
I ask if you ran the meteor commands in a non-administrator prompt because running meteor, even once, with an administrator prompt can wreck the file permissions on meteor and your project, rendering meteor unusable.
It’s a frequent source of issues on Windows because it’s such an easy mistake to make after installing.
I also note that you’re working on D:\ drive. I’ve never managed to get Meteor working outside of C:\ drive (though I know others that have). Try using meteor on C:\ drive first to check if it’s a drive path resolution issue
Hi,
I get the same error when trying to create a hello-world project on C: unit
C:\repos>meteor create hello-world
C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
throw error;
^
Error: Error: Could not install npm dependencies for test-packages: Command failed: C:\windows\system32\cmd.exe /c C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\bin\npm.cmd install --production=false
npm ERR! write after end
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USUARIO\AppData\Roaming\npm-cache\_logs\2018-07-06T05_19_25_754Z-debug.log
npm ERR! write after end
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\USUARIO\AppData\Roaming\npm-cache\_logs\2018-07-06T05_19_25_754Z-debug.log
at Object.error (C:\tools\utils\buildmessage.js:430:11)
at C:\tools\cli\default-npm-deps.js:36:20
at C:\tools\utils\buildmessage.js:334:18
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at C:\tools\utils\buildmessage.js:333:36
at exports.EnvironmentVariable.withValue (C:\tools\utils\fiber-helpers.js:89:14)
at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
at Object.install (C:\tools\cli\default-npm-deps.js:27:27)
at Command.func (C:\tools\cli\commands.js:807:36)
at C:\tools\cli\main.js:1531:15
C:\repos>
I did not install mongoDb or node? Are those needed?
Do you know anyone who codes meteor projects on Windows 10?
@jpfernandezl I am running my project on same meteor version 1.7.0.3 on windows 10.
MongoDB for sure does not need to be installed as meteor ships with a mini mongo which you can use.
Not sure about nodejs fully but looking at the logs you supplied, meteor is using npm command from within meteor itself.
Check C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\bin\npm.cmd install --production=false.
The logs also show that full output is available on C:\Users\USUARIO\AppData\Roaming\npm-cache\_logs\2018-07-06T05_19_25_754Z-debug.log, can you check & post this output as well? Probably this will provide more information on your problem.
Running the app or creating will not require you to have adminstrator access or running cmd with adminstrator mode.
Half the devs where I work use Meteor on Windows 10 and we deploy our apps on kiosk machines running Windows 10. It definitely does work
My guess is that it is a file permissions error, likely because a meteor command was run in an administrator level prompt.
First, do post up the npm error logs that @nileshparab mentioned
Then try doing a reinstall of meteor
// Administrator prompt
choco uninstall meteor -y
choco install meteor -y
// New user level prompt
c:\
cd repos
meteor create hello-world
cd hello-world
meteor run
The following is the bottom of file content from C:\Users\USUARIO\AppData\Roaming\npm-cache_logs\2018-07-06T05_19_25_754Z-debug.log
File is too large and I can not attach a file here.
684 silly decomposeActions finalize punycode@1.3.2
685 silly decomposeActions refresh-package-json punycode@1.3.2
686 silly decomposeActions preinstall url@0.11.0
687 silly decomposeActions build url@0.11.0
688 silly decomposeActions install url@0.11.0
689 silly decomposeActions postinstall url@0.11.0
690 silly decomposeActions finalize url@0.11.0
691 silly decomposeActions refresh-package-json url@0.11.0
692 silly decomposeActions preinstall util@0.10.3
693 silly decomposeActions build util@0.10.3
694 silly decomposeActions install util@0.10.3
695 silly decomposeActions postinstall util@0.10.3
696 silly decomposeActions finalize util@0.10.3
697 silly decomposeActions refresh-package-json util@0.10.3
698 silly decomposeActions preinstall assert@1.4.1
699 silly decomposeActions build assert@1.4.1
700 silly decomposeActions install assert@1.4.1
701 silly decomposeActions postinstall assert@1.4.1
702 silly decomposeActions finalize assert@1.4.1
703 silly decomposeActions refresh-package-json assert@1.4.1
704 silly decomposeActions preinstall util-deprecate@1.0.2
705 silly decomposeActions build util-deprecate@1.0.2
706 silly decomposeActions install util-deprecate@1.0.2
707 silly decomposeActions postinstall util-deprecate@1.0.2
708 silly decomposeActions finalize util-deprecate@1.0.2
709 silly decomposeActions refresh-package-json util-deprecate@1.0.2
710 silly decomposeActions preinstall readable-stream@2.3.6
711 silly decomposeActions build readable-stream@2.3.6
712 silly decomposeActions install readable-stream@2.3.6
713 silly decomposeActions postinstall readable-stream@2.3.6
714 silly decomposeActions finalize readable-stream@2.3.6
715 silly decomposeActions refresh-package-json readable-stream@2.3.6
716 silly decomposeActions preinstall stream-browserify@2.0.1
717 silly decomposeActions build stream-browserify@2.0.1
718 silly decomposeActions install stream-browserify@2.0.1
719 silly decomposeActions postinstall stream-browserify@2.0.1
720 silly decomposeActions finalize stream-browserify@2.0.1
721 silly decomposeActions refresh-package-json stream-browserify@2.0.1
722 silly decomposeActions preinstall vm-browserify@0.0.4
723 silly decomposeActions build vm-browserify@0.0.4
724 silly decomposeActions install vm-browserify@0.0.4
725 silly decomposeActions postinstall vm-browserify@0.0.4
726 silly decomposeActions finalize vm-browserify@0.0.4
727 silly decomposeActions refresh-package-json vm-browserify@0.0.4
728 silly decomposeActions preinstall xtend@4.0.1
729 silly decomposeActions build xtend@4.0.1
730 silly decomposeActions install xtend@4.0.1
731 silly decomposeActions postinstall xtend@4.0.1
732 silly decomposeActions finalize xtend@4.0.1
733 silly decomposeActions refresh-package-json xtend@4.0.1
734 silly decomposeActions preinstall stream-http@2.8.1
735 silly decomposeActions build stream-http@2.8.1
736 silly decomposeActions install stream-http@2.8.1
737 silly decomposeActions postinstall stream-http@2.8.1
738 silly decomposeActions finalize stream-http@2.8.1
739 silly decomposeActions refresh-package-json stream-http@2.8.1
740 silly decomposeActions fetch regenerator-runtime@0.12.0
741 silly decomposeActions extract regenerator-runtime@0.12.0
742 silly decomposeActions preinstall regenerator-runtime@0.12.0
743 silly decomposeActions build regenerator-runtime@0.12.0
744 silly decomposeActions install regenerator-runtime@0.12.0
745 silly decomposeActions postinstall regenerator-runtime@0.12.0
746 silly decomposeActions finalize regenerator-runtime@0.12.0
747 silly decomposeActions refresh-package-json regenerator-runtime@0.12.0
748 silly decomposeActions fetch @babel/runtime@7.0.0-beta.52
749 silly decomposeActions extract @babel/runtime@7.0.0-beta.52
750 silly decomposeActions preinstall @babel/runtime@7.0.0-beta.52
751 silly decomposeActions build @babel/runtime@7.0.0-beta.52
752 silly decomposeActions install @babel/runtime@7.0.0-beta.52
753 silly decomposeActions postinstall @babel/runtime@7.0.0-beta.52
754 silly decomposeActions finalize @babel/runtime@7.0.0-beta.52
755 silly decomposeActions refresh-package-json @babel/runtime@7.0.0-beta.52
756 silly decomposeActions preinstall meteor-node-stubs@0.4.1
757 silly decomposeActions build meteor-node-stubs@0.4.1
758 silly decomposeActions install meteor-node-stubs@0.4.1
759 silly decomposeActions postinstall meteor-node-stubs@0.4.1
760 silly decomposeActions finalize meteor-node-stubs@0.4.1
761 silly decomposeActions refresh-package-json meteor-node-stubs@0.4.1
762 silly install executeActions
763 silly doSerial global-install 464
764 verbose correctMkdir C:\Users\USUARIO\AppData\Roaming\npm-cache_locks correctMkdir not in flight; initializing
765 timing audit compress Completed in 2ms
766 info audit Submitting payload of 1925bytes
767 verbose lock using C:\Users\USUARIO\AppData\Roaming\npm-cache_locks\staging-c7ef383037b37a8d.lock for C:\repos\hello-world\node_modules.staging
768 silly doParallel extract 4
769 silly extract core-js@2.5.7
770 silly extract meteor-node-stubs@0.4.1
771 silly extract regenerator-runtime@0.12.0
772 silly extract @babel/runtime@7.0.0-beta.52
773 silly tarball trying core-js@^2.5.7 by hash: sha512-RszJCAxg/PP6uzXVXL6BsxSXx/B05oJAQ2vkJRjyjrEcNVycaqOmNb5OTxZPE3xa5gwZduqza6L9JOCenh/Ecw==
774 silly tarball trying meteor-node-stubs@^0.4.1 by hash: sha512-UO2OStvLOKoApmOdIP5eCqoLaa/ritMXRg4ffJVdkNLEsczzPvTjgC0Mxk4cM4R8MZkwll90FYgjDf5qUTJdMA==
775 silly tarball trying regenerator-runtime@^0.12.0 by hash: sha512-SpV2LhF5Dm9UYMEprB3WwsBnWwqTrmjrm2UZb42cl2G02WVGgx7Mg8aa9pdLEKp6hZ+/abcMc2NxKA8f02EG2w==
776 silly tarball trying @babel/runtime@^7.0.0-beta.51 by hash: sha1-PztCuCuStOGig/x43xuy/Uuo0Mc=
777 silly tarball no local data for core-js@^2.5.7. Extracting by manifest.
778 silly extract regenerator-runtime@^0.12.0 extracted to C:\repos\hello-world\node_modules.staging\regenerator-runtime-b8ab8021 (76ms)
779 verbose stack Error: write after end
779 verbose stack at writeAfterEnd (_stream_writable.js:236:12)
779 verbose stack at PassThrough.Writable.write (_stream_writable.js:287:5)
779 verbose stack at PassThrough.Writable.end (_stream_writable.js:563:10)
779 verbose stack at ReadEntry.entry.on (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\pacote\lib\extract-stream.js:19:41)
779 verbose stack at emitOne (events.js:121:20)
779 verbose stack at ReadEntry.emit (events.js:211:7)
779 verbose stack at ReadEntry.emit (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\minipass\index.js:309:30)
779 verbose stack at ReadEntry.[maybeEmitEnd] (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\minipass\index.js:257:12)
779 verbose stack at ReadEntry.end (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\minipass\index.js:167:27)
779 verbose stack at Unpack.[consumeBody] (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\pacote\node_modules\tar\lib\parse.js:210:13)
779 verbose stack at Unpack.[consumeChunkSub] (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\pacote\node_modules\tar\lib\parse.js:391:40)
779 verbose stack at Unpack.[consumeChunk] (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\pacote\node_modules\tar\lib\parse.js:362:30)
779 verbose stack at Unzip.(anonymous function).on.chunk (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\pacote\node_modules\tar\lib\parse.js:291:59)
779 verbose stack at emitOne (events.js:116:13)
779 verbose stack at Unzip.emit (events.js:211:7)
779 verbose stack at Unzip.emit (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\minipass\index.js:309:30)
779 verbose stack at Unzip.write (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\minipass\index.js:104:17)
779 verbose stack at Unzip.write (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\minizlib\index.js:284:29)
779 verbose stack at Unpack.write (C:\Users\USUARIO\AppData\Local.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\pacote\node_modules\tar\lib\parse.js:307:19)
779 verbose stack at PassThrough.ondata (_stream_readable.js:639:20)
779 verbose stack at emitOne (events.js:116:13)
779 verbose stack at PassThrough.emit (events.js:211:7)
780 verbose cwd C:\repos\hello-world
781 verbose Windows_NT 10.0.15063
782 verbose argv “C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\bin\node.exe” “C:\Users\USUARIO\AppData\Local\.meteor\packages\meteor-tool\1.7.0_3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\npm\bin\npm-cli.js” “install” “–production=false”
783 verbose node v8.11.3
784 verbose npm v5.10.0
785 error write after end
786 verbose exit [ 1, true ]
Did your try to right click cmd and run as adminitrator?
Unfortunately can’t see anything obvious in the logs. Can you try re-installing and being really careful not to run Meteor as an administrator?
@jpfernandezl could not find a pointer in logs. You should try reinstalling @coagmano stated. If the problem still persists, install node 8.11.3 (which meteor uses) & npm 6.x on machine & try again. Just blindly trying this because I found a slightly similar problem here.
@coagmano You were right, thank you so much.
You saved my ass for the second time.
WINDOWS USERS NEVER RUN METEOR COMMANDS AS ADMINISTRATOR.
Thanks for you too @nileshparab
By the way, you can not run meteor projects from D: unit, only C: unit