I am new to Meteor and Telescope
I installed Meteor, NodeJs and Meteorite. cloned Telescope. when i run meteor from Telescope folder to start the Telescope Meteor project. i get following error
λ meteor
[[[[[ E:\Work\FutureHunt\Git\Telescope ]]]]]
=> Started proxy.
=> Started MongoDB.
rss: updating npm dependencies -- rss...
mailchimp: updating npm dependencies -- mailchimp...
=> Errors prevented startup:
While building the application:
error: no such package: 'crypto-md5'
error: no such package: 'momentjs'
error: no such package: 'iron-router'
error: no such package: 'fast-render'
error: no such package: 'spin'
error: no such package: 'autoform'
error: no such package: 'collection2'
error: no such package: 'jquery-hotkeys'
error: no such package: 'marked'
error: no such package: 'bootstrap3-datepicker'
error: no such package: 'subs-manager'
error: no such package: 'telescope-module-embedly'
While building package `telescope-tags`:
error: no such package: 'simple-schema'
error: no such package: 'iron-router'
While building package `telescope-search`:
error: no such package: 'simple-schema'
error: no such package: 'iron-router'
=> Your application has errors. Waiting for file change.
However. when i create a new project of meteor using "meteor create newproject" and run it. it works fine.
I am also using latest Telescope version. and meteor is in my PATH variable. i can't figure out the error.
According to this:
https://github.com/oortcloud/meteorite/issues/65#issuecomment-11428236
you need to manually copy the source for each of those packages into your telescope project directory.
Overall, I suspect it would be easier to do your Meteor development inside a virtual machine.
Related
I wrote an npm package that uses 'puppeteer' as a dependency.
My project uses that package as dependency. When i installed dependencies and run. I got the following error message.
Error: Could not find expected browser (chrome) locally. Run npm install to download the correct Chromium revision (982053).
I don't know why and how to fix it, thanks
Installed electron#4.0.0 (also tried #4.0.7) and installed grpc and #grpc/proto-loader. When I launch electron I get a runtime error
Uncaught Error: Failed to load gRPC binary module because it was not installed for the current system
Expected directory: electron-v4.0-darwin-x64-unknown
Found: [node-v64-darwin-x64-unknown]
This problem can often be fixed by running "npm rebuild" on the current system
Of course I tried running the suggested solution, npm rebuild, but that did not solve the problem. I also tried rebuilding the grpc module
npm rebuild grpc --build-from-source --runtime=electron --target=4.0.0 --target_archx64 --dturl=https://atom.io/download/electron
I tried uninstalling everything and starting from scratch. We're cloning the electron quick start repo and so after cloning and installing modules I installed grpc targeting a specific version
npm install grpc --runtime=electron --target=<electron version>
Which resulted in the same error so then I tried rebuilding
npm install --save-dev electron-rebuild // to rebuild grpc module
And if I delete node_modules and package-lock.json and then re-install npm install I get a success message (don't pay attention to the version, I'm watching my versions are matching) which looks like the "missing" module was installed
node-pre-gyp WARN Using request for node-pre-gyp https download
[grpc]
Success: "/../electron/node_modules/grpc/src/node/extension_binary/node-v64-darwin-x64-unknown/grpc_node.node" is installed via remote
protobufjs#6.8.8 postinstall /../electron/node_modules/protobufjs
node scripts/postinstall
electron#4.0.8 postinstall /../electron/node_modules/electron
node install.js
I found the answer here:
https://github.com/grpc/grpc-node/issues/762
Still, the solution I tried is the solution I needed. Not sure what I was doing wrong initially!
For future Googlers the summary is this:
The grpc_node module seems to be compiled for NODE_MODULE_VERSION=64,
but Electron 4 since 4.0.4 switched ... to
specifying NODE_MODULE_VERSION=69 and there is a mismatch at runtime
trying to load the module.
So, what I did to solve was
Clone the electron quick start repo
Uninstall the version of electron that came with quick start
Install electron#4.0.0
Install gRPC with target to 4.0.0
npm install grpc --runtime=electron --target=4.0.0
I am working on a nodejs project. I get below error when launch the application.
Failed to load gRPC binary module because it was not installed for the current system
extensionHostProcess.js:293
Expected directory: node-v57-darwin-x64-unknown
Found: [node-v64-darwin-x64-unknown]
This problem can often be fixed by running "npm rebuild" on the current system
Original error: Cannot find module '/Users/dev/node_modules/firebase/node_modules/grpc/src/node/extension_binary/node-v57-darwin-x64-unknown/grpc_node.node
From the description it means there are unmatched native dependencies version related to firebase. I tried npm rebuild which doesn't seem to work. I am using node version:
node: v8.9.4
npm: 6.2.0
How can I fix the dependencies issue? Should I try with particular node version or should I rebuilt some native libraries?
So I did not have installed Node before, just standard Laravel. Today I installed Node.js 8 and now one of my older projects tells me the following in the console:
app.js:66591 Uncaught Error: Module build failed: ModuleBuildError: Module build failed: Error: Missing binding /node_modules/node-sass/vendor/darwin-x64-57/binding.node
Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 8.x
Found bindings for the following environments:
- OS X 64-bit with Node.js 6.x
This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass --force` to build the binding for your current environment.
Unfortunately, 'npm rebuild node-sass --force' doesn't change anything. I tried to install either Node 6 or 8, but I cannot get rid of the error (site is still working anyway, is Laravel using Node only for npm?).
So what's the solution for this?
I package my app with nw.js v0.12.3 and I'm use dns node.js module. When I started my app with 'nw .' all works fine. But when I package my app with nw-packager I have an error 'Uncaught error: No module dns'.
You need to install the dns module via npm install dns --save (not --save-dev) so it's marked as a post-development dependency ("dependencies": in your package.json file instead of "devDependencies":) and is packaged with your app.
Then you should be able to check that the dns module is packed with your code and the nwjs runtime using a tool such as 7-Zip.
nw-packager uses nw-builder under the hood so any manifest options (package.json) that are documented in nw-builder apply to nw-packager