I'm getting this error when I try typing $modulus deploy into terminal from my app directory:
Determining Meteor version...
Meteor version: 1.1.0.2
Bundling Meteor App...
undefined
[Error] Error: Command failed: /bin/sh -c cd /Users/xx/Projects/Project1 && meteor bundle --directory /Users/xx/Projects/Project1/.demeteorized
This command has been deprecated in favor of 'meteor build', which allows you
to build for multiple platforms and outputs a directory instead of a single
tarball. See 'meteor help build'for more information.
WARNING: The output directory is under your source tree.
Errors prevented bundling:
While building the application:
client/Project1.js:138:29: Unexpected token =
I get the same result with $demeteorizer. It worked on an old version of the app, then I added some features in new branch, merged, and now I'm getting this error.
Already tried:
sudo npm update -g modulus
Turns out it was an actual error in my code. I had an extra closing curly brace somewhere.
Related
So I'm a beginner with Sanity.IO and what happened was when I first created my first project everything went perfect, but I accidently deleted some important files in my VS-code which crashed my site which forced me to start over but now
sanity init
is not starting a new project. This is the error I'm receiving:
`
You're setting up a Sanity.io project!
We'll make sure you're logged in with Sanity.io.
Then, we'll install a Sanity Studio for your project.
Press ctrl + C at any time to quit.
Looks like you already have a Sanity-account. Sweet!
Error: Failed to communicate with the Sanity API:
read ECONNRESET
at C:/Users/xxx/AppData/Roaming/npm/node_modules/#sanity/cli/bin/sanity-cli.js:4860:4515
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async e.default (C:/Users/xxx/AppData/Roaming/npm/node_modules/#sanity/cli/bin/sanity-cli.js:4860:4
`
I have deleted my project from Sanity.IO studio but still I'm receiving the same error.
I have tried the following steps:
npm install -g #sanity/cli
sanity init
I get the same error.
npm install -g #sanity/cli
sanity install
sanity init
I get the same error.
I have also tried
npx install --global #sanity/cli
npx #sanity/cli init
I get the same error. I can't create a project.
Also if I try sanity logout it gives me error:
Failed to communicate with the Sanity API:
read ECONNRESET
I looking at every google link to find any solution but I have not.
Hi wonderful people of stackoverflow!
Background
I have an Angular 9 application and CI set up with Codeship. This has been running fine until about two weeks ago when suddenly it stopped working after I upgraded from Angular 7.
Set up commands:
nvm ls
nvm install v10.15.1
nvm use v10.15.1
gem install rb-inotify -v 0.9.10
gem install sass
npm install -g firebase-tools#6.12.0
npm i firebase-functions#3.3.0
yes | npm install -g #angular/cli#9.1.12
npm i
cd functions
nvm use v10.15.1
npm i
cd ..
Which runs as expected. I have checked the versions in the CI environment with npm outdated, which show me that the correct versions are being installed the same as local:
Deploy script:
firebase use default
firebase functions:config:set test="test" --token "$FIREBASE_TOKEN"
firebase deploy --token "$FIREBASE_TOKEN"
Error:
firebase use default is successful, but firebase functions:config:set test="test" --token "$FIREBASE_TOKEN" now returns:
Error: HTTP Error: 404, Method not found.
Notes:
I've reset up the $FIREBASE_TOKEN with the new cli and can confirm that this probably isn't the issue, because when the token is incorrect (I removed the last character from the TOKEN), it throws a different error stating this.
I can also confirm that the same script run locally works and deploys just fine - so while I can get around the problem this way, it isn't an ideal or long term solution.
Any ideas or help would be genuinely appreciated as I'm somewhat lost as to what to do next?
This seems to be related with firebase-tools version. When I installed the same version as you have (6.12.0) I got the same error.
I have tried on new version (I have 8.7.0) and it is working fine with one more remark. When I tried exactly the same command as you have error:
Error: Invalid argument, each config value must have a 2-part key (e.g. foo.bar).
So working command will be like this:
firebase functions:config:set test.test="test"
If you need old version of firebase-tools I tested few other versions and it seems that this is working since version 7.1.0.
For anyone else having this issue - I never managed to solved this sorry. However I migrated my CI over to use GitHub Actions easily and it all works without any issue.
[react-pocketscholar (master)]$ meteor --version
/Users/ftrflyr/.meteor/packages/meteor-tool/.1.3.4_3.1v4v008++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:165
throw error;
^
Error: EEXIST, symlink '/Users/ftrflyr/.meteor/packages/meteor-tool/.1.3.4_3.1v4v008++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle'
[react-pocketscholar (master)]$ meteor -v
/Users/ftrflyr/.meteor/packages/meteor-tool/.1.3.4_3.1v4v008++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:165
throw error;
^
Error: EEXIST, symlink '/Users/ftrflyr/.meteor/packages/meteor-tool/.1.3.4_3.1v4v008++os.osx.x86_64+web.browser+web.cordova/mt-os.osx.x86_64/dev_bundle'
1. Global tool version of meteor command
Find version by:
meteor --version
2. Project version of meteor
A project stays at the meteor version which it was created with unless manually upgraded. Find this by running:
cat .meteor/release
Another way to do this is to open up your Javascript console in the browser and type:
console.log(Meteor);
This is very useful for me as I'm running Ubuntu on a Chromebook so I don't need to stop my local server to check which version I'm currently running.
Please note the server does need to be running (localhost:3000) for this command to work.
You have to be in a meteor project repository and type meteor --version
My meteor application works locally. When I bundle it (using meteor bundle myapp.tgz), upload it on my server and launch it, I have the following error upon opening the page on Chrome console:
Uncaught SyntaxError: Unexpected token <
On Firefox console:
SyntaxError: syntax error
[Break On This Error]
<!DOCTYPE html>
In order to try to find the origin of the error, I used an old bundle that was working. I can see the problem is that the files in static_cachable are not found.
Meteor is still trying to use the files from the old bundle.
If I rename the new bundled files in static_cachable to the old name then It works.
I checked in all files contained by the root of the bundle folder and references are correct (they are pointing to the new names).
It there some cache somewhere that keep the reference to the old static_caches files ?
To avoid the error, one has to restart Meteor after deployement :
rm -rf bundle
tar -zxf myapp.tar.gz
cd bundle/server/node_modules/
rm -r fibers
npm install fibers#1.0.0
export PORT=32632
export MONGO_URL=mongodb://meteor:**#localhost:18700/moviegrid
export ROOT_URL='mydomain.com'
nohup node bundle/main.js &
Look at the javascript console when you load your app locally and check if there is no error. If there is some, correct them before bundling/deploy.
This may not be your problem but according to http://docs.meteor.com/#deploying:
For now, bundles will only run on the platform that the bundle was created on. To run on a different platform, you'll need to rebuild the native packages included in the bundle. To do that, make sure you have npm available, and run the following:
$ cd bundle/server/node_modules
$ rm -r fibers
$ npm install fibers#1.0.0
Consider installing meteor on your server, cloning your app directory and using meteor run inside the directory to see if the app runs in development on the server.
If it successfully launches in development then bundle it on the server and use those files. Or just run with meteor --production
when i do this:
$ mrt create myapp
$ cd myapp
$ mrt
i get this error message:
livedata: updating npm dependencies -- sockjs, websocket...
No dependency info in bundle. Filesystem monitoring disabled.
=> Errors prevented startup:
Exception while bundling application:
Error: Command failed: npm WARN package.json packages-for-meteor-smartpackage-livedata#0.0.0 No README.md file found!
i have this from the new "discover meteor" book by sasha greif.
thanks in advance.
I had a similar problem as I was following through the Discover Meteor book as well. It might be the same error you are having but I can't remember it exactly, it was rather long and suggested running mrt as root/administrator. Also, I'm not sure if the error I was having was related to the version of Node.js that I was using (0.10.6 on Ubuntu).
Thanks to a comment posted on github by Apendua (https://github.com/apendua) I was able to run mrt successfully without having to run as root/administrator.
Here is what he found:
"What I've seen so far is the follwing. After calling:
sudo npm install -g meteorite
there is a mysterious tmp dir in my home with content owned by root. I don't think it's distribution specific since I've experienced this on Ubuntu 12.10 as well as on Ubuntu 13.04. Also, the content of .npm dir in my home is sometimes - but sometimes it is not - owned by root. Getting rid of tmp and changing privilages on .npm solevd the issue for me. No need to sudo mrt any more."