I’m stuck in a situation where I’m not able to build my meteor app (Version 1.4.3.1) anymore.
When calling
meteor build ~/builddir --server subdomain.domain.com
I suddenly get the error message
'build' is not a meteor command. See 'meteor --help'
I know that any action before the first occurrence of the error is probably the cause.
The last thing I remember was the call of a chain of commands like
meteor reset && meteor build ~/_builddir --server subdomain.domain.com && cd ~/_builddir/android && cp release-unsigned.apk release-tosign.apk && jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore .keystorefile release-tosign.apk keystore_alias && mv release-tosign.apk release-signed.apk && ~/Library/Android/sdk/build-tools/25.0.3/zipalign 4 release-signed.apk finalBuild_signed.apk && cd ~/meteordir
in Mac Terminal / VS Code terminal. (I don't remember exactly where I started the command chain...
Unfortunately I couldn’t find any similar question here that brings me to a idea or a solution.
After the first occurrence I tried to
meteor reset
(this is still a known command for meteor), but I got the same error message
I deleted the node_modules and re-installed all packages
meteor npm i
but I got the same error message
I tried to update to the meteor version 1.4.3.1 (used in this project)
meteor update --release 1.4.3.1
this was not working because cli told me it’s already installed, so I tried to up- and downgrade via
meteor update --release 1.4.3.2
and
meteor update --release 1.4.3.1
but I got the same error message
so I started a new installation
curl "https://install.meteor.com/?release=1.4.3.1" | sh
but I got the same error message
I alway made the call inside of a meteor project folder, as I always had been doing before.
My gut feeling told me, this is a quite simple thing. Something I’ve forgotten … but I’m just a newbie hoping anybody can help.
Best regards