Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

jskos-tools

Package Overview
Dependencies
Maintainers
1
Versions
83
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

jskos-tools - npm Package Compare versions

Comparing version 1.0.11 to 1.0.12

7

package.json
{
"name": "jskos-tools",
"version": "1.0.11",
"version": "1.0.12",
"description": "Tools for working with the JSKOS data format.",

@@ -53,2 +53,3 @@ "homepage": "https://github.com/gbv/jskos-tools",

"lint-staged": "^10.2.11",
"lodash": "^4.17.20",
"mocha": "^7.2.0",

@@ -60,5 +61,3 @@ "mocha-eslint": "^6.0.0",

},
"dependencies": {
"lodash": "^4.17.19"
}
"dependencies": {}
}

@@ -72,7 +72,9 @@ # JSKOS Tools

```bash
git clone https://github.com/gbv/jskos-tools.git
cd jskos-tools
npm i jskos-tools
```
We are also providing browser bundles:
- Development (not minified, ~68K): https://cdn.jsdelivr.net/npm/jskos-tools/dist/jskos-tools.js
- Production (minified, ~26K): https://cdn.jsdelivr.net/npm/jskos-tools@1
## Usage

@@ -85,9 +87,4 @@ If you installed jskos-tools via npm, use it like this:

We are also providing browser bundles:
- Development (not minified, ~190K): https://cdn.jsdelivr.net/npm/jskos-tools/dist/jskos-tools.js
- Production (minified, ~66K): https://cdn.jsdelivr.net/npm/jskos-tools/
- It is recommended to pin the version to the desired major version number, e.g.: https://cdn.jsdelivr.net/npm/jskos-tools@1
Using the browser bundles will provide you with the `jskos` global variable.
Including these bundles will provide you with the `jskos` global variable.
See <https://gbv.github.io/jskos-tools/> for full API documentation of

@@ -451,8 +448,19 @@ [module jskos-tools](https://gbv.github.io/jskos-tools/module-jskos-tools.html).

## Publish
Please work on the `dev` branch during development (or better yet, develop in a feature branch and merge into `dev` when ready).
To publish a new version on npm after committing your changes, follow these steps:
When a new release is ready (i.e. the features are finished, merged into `dev`, and all tests succeed), follow these steps:
```bash
npm version patch # or minor, or major
# Increment version (patch/minor/major)
npm version patch
# Push dev (without tags!)
git push
# Switch to master branch
git checkout master
# Merge dev (should fast-forward merge)
git merge dev
# Push masater (including tags)
git push --tags origin master
# Switch back to dev (don't accidentally work on master)
git checkout dev
```

@@ -459,0 +467,0 @@

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc