Security News
NIST Misses 2024 Deadline to Clear NVD Backlog
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.
everlive-sdk
Advanced tools
The Everlive JavaScript SDK, also known as the Backend Services JavaScript SDK, allows you to use the backend services provided by Telerik Platform by Progress from any JavaScript application.
Internally, Telerik Platform by Progress uses the Backend Services JavaScript SDK in:
The Backend Services JavaScript SDK is packaged with Browserify for all environments except for Node.js, where you can use the code found in the src
folder directly.
For additional topics, see the official Telerik Platform by Progress documentation: Getting Started with the Backend Services JavaScript SDK.
Depending on your preferred sourcing method, do the following to install the Backend Services JavaScript SDK.
NPM
npm install
Bower
bower install everlive
Online copy
https://bs-static.cdn.telerik.com/latest/everlive.all.min.js
Download
https://bs-static.cdn.telerik.com/sdk/latest/javascript/EverliveSDK.JS.zip
Use the following line of code to add the Backend Services JavaScript SDK to your project depending on your JavaScript environment of choice:
Browser:
<script src="path/to/sdk/everlive.all.js"></script>
Node.js:
var Everlive = require('everlive-sdk');
Cordova (Android, iOS, Windows Phone):
<script src="path/to/sdk/everlive.all.js"></script>
NativeScript (Android, iOS):
var Everlive = require('everlive-sdk');
ECMAScript 6 and TypeScript:<br >Note: Use Typescript compiler version 2.0 or later.
import Everlive from 'everlive-sdk'
The source code is available in the src
folder. The entry point of the application is index.everlive.ts
.
To build the source code, run either of the following commands. They output everlive.js
and everlive.map
to the project root.
Build once:
npm run build
Rebuild automatically on each change:
npm run watch
To make a distribution build, use the following command:
npm start
It outputs the following files:
|-- root
|-- dist
|-- everlive.all.js
|-- everlive.all.map
|-- everlive.all.min.js
|-- license
|-- readme
|-- declarations (contains the TS declarations)
|-- EverliveSDK.JS.zip
To learn how to use the Backend Services JavaScript SDK in your applications, head to the official documentation.
The source code features automated tests for each supported environment in the test
folder. There are mobile projects for Cordova and Nativescript located in test/mobile/Everlive(Cordova|NativeScript)
.
Currently there are automated tests only for Android.
External files for Node.js and PhantomJS are located in test/external
.
You need to set up the following on your system before you can run tests.
The easiest way to run tests is to open the test suite's .html file in a web browser. For example, open test/suites/everlive-caching/everlive-caching.html
to run the entire suite of tests for the Caching feature. The other options to run tests are explained below.
To run all tests against all platforms sequentially, run:
$ npm run test
Most of the time, you will want to run tests against a specific platform:
$ npm run test --platform {desktop | nodejs | cordova | nativescript}
If you want to run only a specific suite, specify it using the suite
flag. By convention, it tries to find the suite in test/suites/{suite-name}/{suite-name}.html
.
$ npm run test --platform cordova --suite everlive-files
The test results appear as console messages but also output to files called tap reports in test/testResults(platform).tap
. For example:
1..770
ok 0 Everlive data - Online EmailSubscribers Everlive data - offline control offline should throw when offline not enabled
ok 1 Everlive data - Online EmailSubscribers Everlive data - offline control isOffline should throw when offline not enabled
not ok 2 Everlive data - Online EmailSubscribers Everlive data - offline control isOnline should throw when offline not enabled - AssertionError: expected 'expected false to be truthy' to equal 'You have instantiated the SDK without support for offline storage'
By default, each platform's tests are run against a different backend-services project. This setting can be changed in test/suites/externalconfig.template.js
.
When writing tests, add them to test/suites/everlive-{suite-name}
folders. Each such folder must contain a everlive-{suite-name}.html
file which specifies its tests.
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Everlive tests</title>
</head>
<body>
<script src="../../TestRunner.js" data-js="everlive-caching.test.js"></script>
</body>
</html>
This is what a simple test looks like:
describe("Test", function () {
ok(1 === 1);
}
The combination of HTML file and JavaScript file loads all scripts and CSS needed by default (see test/TestRunner.js
), creates a div[id=mocha]
, and adds the scripts specified in the data-js
attribute.
The TestRunner can be accessed from window.runner
.
FAQs
Backend Services SDK
The npm package everlive-sdk receives a total of 278 weekly downloads. As such, everlive-sdk popularity was classified as not popular.
We found that everlive-sdk demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.
Security News
Cloudflare has launched a setup wizard allowing users to easily create and manage a security.txt file for vulnerability disclosure on their websites.
Security News
The Socket Research team breaks down a malicious npm package targeting the legitimate DOMPurify library. It uses obfuscated code to hide that it is exfiltrating browser and crypto wallet data.