Im working on a Vue App. I develop it on Windows and it works fine - no errors. But when I copy my project (except of the node modules) to my Debian server, install all dependencies and start it I get this error: Segmentation fault.
I found the error is based in the src folder. If I copy any file from there (except the assets folder / files) the Segmentation fault error appears but not if I copy my modified config and build files.
ps. When I copy my project to a new folder on Windows and install the dependencies it works and the Vue Client server is running.
And if I create a new vue client project on my Debian server and let it run it also works ... till the moment I copy my src folder.
Solution: I downgraded Node from 6.10 to 6.9.5
To use an older version is often the solution.
source (german): https://www.gutefrage.net/frage/segmentation-fault-error-beim-vuejs-client---debian-server?foundIn=login&randomReloadId=981505#comment-151824131
Related
After installing node-pty (an external module used to create pseudo terminals using node js) in a boilerplate electron-forge project; I found it throwing an error that some core module of node-pty is importing another module which nodejs is failing to find.
After some research I discovered that entry point of node-pty is src/index.js, which imports another module called src/unixTerminal.js (this file is imported if the system is running on linux platform and my PC is running on Ubuntu 20.04) and that module tries to import build/Releases/pty.node.js (unixTerminal.js calls many functions imported from pty.node.js, so this package cannot be ommitted) but as a matter of fact build/Releases/pty.node.js is missing and completely absent in the node_modules/node-pty folder of my project where I had installed node-pty
Why does this happen? Is this any fault of myself in installing node-pty, I had installed it directly using npm i command? If a vital file of a module is missing how can it work? Please tell me how can I use node-pty on Linux and why build/Releases/pty.node.js is missing in node-pty's directory?
Since you're using Electron Forge (a crucial detail omitted from the original post), according to this issue I found by googling "node-pty electron forge" you'll need to configure the Electron packager to unpack the pty.node file:
asar: {
unpack: '**/node_modules/node-pty/build/Release/*'
},
I have a project build on react-native version 0.55.4. It was woking fine on old system. I have to change system due to some reasons. I setup on new system, I am able to run project using react-native run-android but when building a signed APK using ./gradlew assembleRelease I am receiving following error.
Task :app:processReleaseGoogleServices
Parsing json file:
<Project-Directory>/android/app/google-services.json
FAILURE: Build failed with an exception.
What went wrong:
Could not list contents of
'<Project-Directory>/node_modules/react-native/scripts/third-party/glog-0.3.4/test-driver'. Couldn't follow symbolic link.
I know this issue is already on stack overflow Invalid symlink in node_modules error when trying to deploy to simulator (RN 0.45). I have tried it. I have also tried following github question.
https://github.com/facebook/react-native/issues/11212
https://github.com/facebook/react-native/issues/14417
https://github.com/facebook/react-native/issues/14548
https://github.com/facebook/react-native/issues/14464
I have also tried following things.
Deleting node modules and reinstalling them
Deleting .bin folder in node modules
Deleting react-native/third_party folder in node modules.
Copying node modules from older system.
Copying third-party and glog-0.3.4 from older system.
Deleting test-driver file inside third-party folder.
Unlinking test-driver file inside third-party folder.
Installing automake-1.16 and creating a new alias of test-driver file inside third-party folder.
My java version is 1.8.0_201. My android studio version is 3.3.2. Projects react native version is 0.55.4. My mac os version is 10.14.4. My x code version is 10.2.
Please help.
Thanks in advance.
Unlinking as below and restart with the cache cleaned
In project folder:
unlink ./node_modules/react-native/scripts/third-party/glog-0.3.4/test-driver
and then stop js server and run:
npm start -- --reset-cache
It should work
I am currently trying to generate native versions of a small meteor app I built. When I run them on iOS or Android via the meteor run command it works and meteor build with --debug also generates an ipa/apk that works as expected. But when I run meteor build without --debug the web view only shows a white screen. Using remote debugging I noticed an injector error. I was wondering why and checked the apk/ipa content. There I recognized that in the debug version under assets/www/application/packages there is a bunch of .js and .js.map files which simply is not there in the non-debug ipa/apk.
In the index.html of the non-debug ipa/apk the imports of these files are also missing.
How can I tell meteor to just copy these obviously required files for non-debug?
When you build, Meteor concatenates and minifies all the JS files into a single bundle, same as Browserify and webpack are doing. That is why you do not see all the script imports.
It does not do it in debug to facilitate live reload / hot code push while you are developing, besides facilitating debugging​ obviously.
See the Meteor guide on building for production.
If you believe this difference causes some issue, you can simulate it in development using the --production flag after meteor run.
This addresses your titled and last question, but may not fix in itself your initial issue.
I have recently been building an Angular2 starter kit for my own use, using various bits and pieces found in tutorials and SO. I now have gulp tasks to bundle the app for production but it won't work without running it through a server, node in this case.
Here is the repo: https://github.com/LGLabGreg/lg-angular2
Basically running gulp dist will bundle the app fine in dist/ folder, but clicking the index.html in that folder doesn't work, the app is stuck on "Loading...". If I serve it with node it works.
Thanks.
That's because when you are serving it from node the baseUrl is set correct /, but when you just click on index.html the baseUrl is set to / which will probably be C:\ (file://). Resulting in the browser trying to obtain all resource from file://. Check your browser console for errors
Sooooo... that's a pickle
I am using IBM Bluemix for a school project.
I have finished the code and I need to send the application to the IBM Bluemix platform.
I am using the cf toolbar and the standar methods for sending the app to the cloud (cf login, cd into the new directory, cf push etc).
Nonetheless, I get the error
Staging Failed: An application could not be detected by any available buildpack
What is causing this and how can I solve it?
Here is a print of the error screen I get when sending the app to Bluemix - With the cf logs associated with the error.
When you push your application to Bluemix your root directory is scanned in order to understand what kind of buildpack should be used. In your case you need the Node.js buildpack, which is used when in your root directory you have the package.json file. It contains all the dependencies your application needs to run and it is used by the buildpack to download all the required libraries. If your application works fine on your machine it means that you have all the required libraries in the node_modules folder. You can use the npm init command to automatically generate the package.json file for all the libraries/middleware you need. Please take a look at Npm init Docs. You can also refer to Bluemix Node.js starter application to see the default package.json.