i am trying to package a simple ember.js example with node webkit in mac-os 10.8 but i am getting the specified error "Running without renderer sandbox". Is there any issue with using ember.js with nodeWebkit b'coz when i am packaging without using ember.js it's working.
The warning message "Running without renderer sandbox" can be ignored. node-webkit doesn't have sandboxes as Chromium does.
Related
I actually only have a Node.js CLI application which I want to package as an AppImage and maybe even with auto-updater functionality. So is it possible to use electron-builder for a Node.js application without Electron?
If not, is there some other tool out there which can bundle a Node.js application into an AppImage?
Background: I am running tests in the Protractor framework against a website written in Angular using Firefox as the browser
The website initially loads with a Server-side render. The follow-up client-side render appears to get interrupted. Angular is available, but nothing in the Dom loads.
Asking Google hasn't helped(none of the Stackoverflow results appeared to be relevant). Didn't see any open issues or closed issues on the Protractor github which appeared to be relevant
I'm not sure what's relevant to the investigation, so starting information:
Firefox version: 65
geckodriver version: v0.24.0 [last]
protractor version: 5.4.1
framework: jasmine
directconnect = true
Has anyone resolved this issue before? Is there additional information which would be relevant. What have I missed? The same tests running against Chrome pass without issue
Im having an issue while trying to solving another one.
Im developping a Rails app on Windows 10, I run into the JavaScript issue that avoid Rails from working, a lot of people solve this issue by Installing Note.JS, some others change UTF-16LE to UTF-8 on routines.rb on ExecJS gem.
None of those solve my issue so I decide to force Rails using Node.JS instead of Windows default JScript by installing Node.JS (I tried with both x64 and x86 versions) and adding
ENV['EXECJS_RUNTIME'] = 'Node'
to my boot.rb ... this drive my into my second error by showing this message on rails server loading process:
There was an error while trying to load the gem 'uglifier'. (Bundler::GemRequireError)
Gem Load Error is: Node.js (V8) runtime is not available on this system
I really appretiate your help! Im driving with those error for a while now and I feel kind of stuck now.
I have an app that I made with yeoman, grunt an angular JS (typical setup - image included below). I'm trying to debug my project with spyjs (or even regular javascript debugging) but I can't seem to get it working when I run "grunt serve" - the file that's loaded from WebStorm clearly isn't going through the grunt server (but localhost:63343 instead). Any ideas how I could configure things properly to get debugging to work?
Here's my SpyJS configuration:
I've also tried localhost:9000 for the URL to trace (which is the port that grunt serve runs on), and I've tried using another node interpreter.
You need using the server your client code runs on (localhost:3000) and not WebStorm built-in webserver to debug your Angular application served by Grunt. See Debugging grunt with Intellij for some hints
Note: haven't tried this with spyjs - only with a regular debugger
You need to upgrade to Webstorm 9. As per spy-js
Node.js tracing is now supported in WebStorm 9 EAP, including multi process and node cluster tracing support.
Then instead of using Spy-js profile, use Spy-js for Node.js profile.
This screenshot is from Webstorm 9 RC.
I am using too the Yeoman generator (AngularJs + grunt), and I am debugging the application using the JavaScript Debug configuration like this:
(source: ignaciosuay.com)
Have a look to this post about how to debug angularJS with Intellij (It should work too for web storm)
I'm using node webkit with the node webkit hipster seed
I have build a native C++ module, using the Leap Motion SDK, which compile and work fine with node-gyp.
Now I'm trying to implement it on node webkit, but I always get "Error: no error" when I require my module. (Yes, it's recompiled with nw-gyp)
I was getting the same error when I was trying my module with node-gyp without leap sdk dlls, so I try to move my dlls in the module build directory, and in the application build directory, but no effect.
I'm using Windows 8, but I will also build on OSx
Strangely, it work by renamming the executable to nw.exe, thanks to https://github.com/geo8bit/nodebob/pull/7