npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

vigour-wrapper

v4.0.8

Published

The native code to wrap vigour apps

Readme

Build Status

Wrapper

Builds a set of native apps from a single javascript codebase.

npm install vigour-wrapper

Dependencies

  • npm 2@ˆ2
  • cocoapods, see http://guides.cocoapods.org/using/getting-started.html (some plugins might require it)

Install

  • Add git+ssh://[email protected]:vigour-io/vigour-native.git#master to dependencies in package.json
  • npm i vigour-native --save (Coming soon)

Usage

Declaring vigour-native as a dependency to a project make an executable called wrapper accessible. You can then build the project with wrapper build or wrapper build -- <platform> (see supported platforms). Configuration is read from the project's package.json[vigour.native].

###Observations:

####SamsungTv

More info about the package.json fields here

####Lg webos Tv For Lg webostv, a manually process is required before run the build script. Lg uses a SDK to generate ipk files, and this SDK is not available on npm. To download the SDK just go to LG developer web site, and follow the steps. If you want to understand more about the SDK CLI you can read more here.

####Tizen Tv If you want to test your project on the TV, you will need to download the Tizen SDK. Today (24/12/2015) the only version that works good is the version 2.4.0, but you can download the latest version on the web site and when you start the installation process, you can specify the version 2.4.0.

  • How to setup the developer mode on the tv ?

    • Go to smart hub and press, 1,2,3,4,5. Then fill the ip field with you machine IP. After that restart the tv on the eletric power(Remove it from the eletric socket).
  • How to see my app on the tv?

    • After the step above ^^^; you will need to run npm run tizentv and import the wgt file on the IDE. Once your peoject was imported, click on the 'remote device manager' in the connection tab. Then insert your TV IP address and do not change the default port. Right click on the project and choose '''run as''' and select your TV.

######Tizen info in package.json: | Key |Value | |---|---| | appName | The name that will be displayed as your app on the tv | | iconPath | The app icon, must be 512x423 pixel JPG or PNG format icon | | yourDomain | The web site domain, Tizen uses it as a kind of identifier (ID) | | appVersion | Application version number. e.g 1.0.0 | | Location | Object that contains name and description for the contries that the app will be available |

More info : config.xml

It May help :

specific details:
  • Use the default folder path when installing the SDK

  • The build process only uses the SDK CLI. It means that you can install only the CLI from SDK the package.

  • ares-package comand is used by the build script to generate the IPK file using the SDK CLI.

  • The IPK file name is generated automatically, it uses the id property in appinfo.json to generate it.

Tests

Most of the tests expect to find the vigour-example repo in the same directory as vigour-native. If that is so, then mocha test/ should do the rest. This of course should be improved eventually, either by making vigour-example a submodule, or by automating the cloning the first time tests are run, or perhaps even something entirely different...

In-script usage

var wrapper = require('vigour-native')
wrapper.build({
  src: './src'
  , dest: './build'
  , splash: './img/splash.png'
  , platforms:
    {
      "web": true
      , "ios": {
        splash: {
          src: './img/splash-ios.png'
        }
      }
      , "android"
      , "wp8"
      , "chromecast"
      , "LG TV"
      , "Samsung TV"
      , "iWatch"
    }
  , plugins: [
    "https://github.com/vigour-io/vigour-native-statusBar#master"
    //, "vigour-native-statusBar" // Coming Soon: via npm
  ]
  , ignoreBuilds: true // Git only
}, function (err, meta) {
    console.log("Build done in " + meta.time "ms")
  })

Also works with promises

var wrapper = require('vigour-native')
  , Promise = require('promise') // `npm i promise`
  , build = Promise.denodeify(wrapper.build)
build({...})
.then(function (meta) {
  console.log("Build done in " + meta.time + "ms")
})
.catch(function (reason) {
  console.error(reason)
})

Bridge

ios

  • app does
bridge.send(pluginId, fnName, opts, cb)
  • bridge does
window
    .webkit
    .messageHandlers
    .vigourBridgeHandler
    .postMessage({ pluginId: 1,
      fnName: 'act',
      opts: {},
      cbId: 2
})
  • native does its stuff, then calls
window.vigour.native.bridgeResult(cbId, error)

or

window.vigour.native.bridgeResult(cbId, null, response)

with error being either an error as described below, or an array of them:

{ message: "string",
  info: {}
}

android

  • app does
bridge.send(pluginId, fnName, opts, cb)
  • bridge does
window
    .NativeInterface
    .send(
      JSON.stringify(
        [ cbId,
          pluginId,
          fnName,
          opts
        ]
      )
    )
  • native does its stuff, then calls
window.vigour.native.bridge.result(cbId, error)

or

window.vigour.native.bridge.result(cbId, null, response)

with error being either an error as described below, or an array of them:

{ message: "string",
  info: {}
}

native

Android

The native code for android is devided in two projects, both found in templates/android:

  • app: the code for the app that contains the WebView that will display the javascript app
  • plugincore: the library of base classes needed for both plugins and the app.

The plugin-core library is released to JCenter and can be added as dependency with the following code:

compile 'io.vigour:plugin-core:0.4.1'

The current version of the plugincore is Download

Supported Platforms

  • [X] web browsers
  • [X] iOS
  • [X] android
  • [X] lg net cast TV (old platform)
  • [X] lg Webos TV (new platform)
  • [X] samsung TV
  • [X] samsung Tizen TV
  • [x] chromecast
  • [ ] iWatch
  • [ ] windows phone

Contacts

Vigour

  • Valerio Barrila, team leader, responsible for team organization and project execution
  • Shawn Inder, main developer, responisble for core components
    • Slack: shawn
    • Skype: shawnfinder
    • Email: [email protected]
    • Phone canada: 1-514-903-9082
    • Phone nl: +31628959682
  • Renan Carvalho, developer, responsible for web and tv's

External collaborators

  • Alexander van der Werff, ios developer
  • Michiel van Liempt, android developer
  • David Bina, plugins developer (ios, android)