NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #3583 most downloaded on npm
Convert Google .p12 keys to .pem keys.
Last release 3 years ago
no release in 18 months
Release timing varies
gaps range from 3 weeks to 12 months
Unknown
no stable releases
29 versions withdrawn
withdrawn after publishing
12 years old
29 releases · first in 2014
## 5.0.0 (2023-08-15) ### ⚠ BREAKING CHANGES * upgrade to Node 14 (#435) ### Miscellaneous Chores * Upgrade to Node 14
## 4.0.1 (2022-08-23) ### Bug Fixes * deps: pin node forge at 1.3.0 (#415) (70316b4) * deps: unpin node-forge (#417) (69b9066) * remove pip install st
One column per quarter.
## 4.0.0 (2022-05-17) ### ⚠ BREAKING CHANGES * update library to use Node 12 (#410) ### Build System * update library to use Node 12
deps: force fixed version of node-forge (#403) (f375cca), closes #397
deps: update dependency node-forge to v1
build: migrate to using main branch
build: use updated repository URL
add gcf-owl-bot[bot] to ignoreAuthors
deps: update dependency node-forge to ^0.10.0
### Bug Fixes * typeo in nodejs .gitattribute
### Bug Fixes * apache license URL
typescript@3.7.x introduced backwards incompatibilities
deps: update node-forge to 0.10.0 (#341) (201f9c3), closes #297 #337
deps: pin TypeScript below 3.7.0
docs: add jsdoc-region-tag plugin
deps: update dependency node-forge to ^0.9.0
docs: link to reference docs section on googleapis.dev
upgrade engines field to >=8.10.0
deps: update node-forge to 0.10.0
This release includes a new shiny version of node-forge!
03-12-2019 12:25 PDT
This release includes a new shiny version of node-forge!
This is a service release very few updates. The only interesting change is the removal of support for Node.js 4.x and 9.x, both of which are out of LT
12-07-2018 09:50 PST
This is a service release very few updates. The only interesting change is the removal of support for Node.js 4.x and 9.x, both of which are out of LTS support.
This release has no functional changes other than it is packaged by npm < 5.7.0 which happens to have a bug where the timestamps on the tarball conten
This release has no functional changes other than it is packaged by npm < 5.7.0 which happens to have a bug where the timestamps on the tarball contents ended up being wrong. See https://github.com/google/google-p12-pem/issues/27 for full details.
The security issue didn't affect this module in actual usage, but was showing up as a vulnerability in security dashboards.
This release only contains dependency and build tooling changes. Notably, the main dependency update is node-forge to ^0.7.4 which includes a security fix. The security issue didn't affect this module in actual usage, but was showing up as a vulnerability in security dashboards.
This is a semver major release that includes *breaking changes* in addition to better support for promises and async/await.
This is a semver major release that includes breaking changes in addition to better support for promises and async/await.
getPem as a named export. Users using require can use const {getPem} = require('google-p12-pem')awaited or thened.Migration should be straight forward. Example:
// before
var gp12 = require('google-p12-pem');
gp12('/path/to/key.p12', function(err, pem) {
console.log(pem); // '-----BEGIN RSA PRIVATE KEY-----\nMIICXQIBAAK...'
})
// now
const {getPem} = require('google-p12-pem');
getPem('/path/to/key.p12', function(err, pem) {
console.log(pem); // '-----BEGIN RSA PRIVATE KEY-----\nMIICXQIBAAK...'
});
// See README for example of using with async/await and promises.
Updated node-forge to ^0.7.1 fixing #8
Updated node-forge to ^0.7.1 fixing #8
Updated node-forge to ^0.6.46
Updated node-forge to ^0.6.46
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →