- SSH2 SFTP Client
- Installation
- Basic Usage
- Breaking Changes in Version 4.x
- Enhancements in Version 4.2.x
- Enhancements in Version 4.1.x
- Documentation
- Methods
- new SftpClient(name) ===> SFTP client object
- connect(config) ===> SFTPstream
- list(path, pattern) ==> Array[object]
- exists(path) ==> boolean
- stat(path) ==> object
- get(path, dst, options) ==> String|Stream|Buffer
- fastGet(remotePath, localPath, options) ===> string
- put(src, remotePath, options) ==> string
- fastPut(localPath, remotePath, options) ==> string
- append(input, remotePath, options) ==> string
- mkdir(path, recursive) ==> string
- rmdir(path, recursive) ==> string
- delete(path) ==> string
- rename(fromPath, toPath) ==> string
- chmod(path, mode) ==> string
- realPath(path) ===> string
- cwd() ==> string
- end() ==> boolean
- Add and Remove Listeners
- Methods
- FAQ
- Change Log
- Logging Issues
- Pull Requests
- Contributors
an SFTP client for node.js, a wrapper around SSH2 which provides a high level convenience abstraction as well as a Promise based API.
Documentation on the methods and available options in the underlying modules can be found on the SSH2 and SSH2-STREAMS project pages.
Current stable release is v4.1.0.
Code has been tested against Node versions 8.16.1, 10.16.3 and 12.9.1
Node versions < 8.x are not supported.
npm install ssh2-sftp-client
let Client = require('ssh2-sftp-client');
let sftp = new Client();
sftp.connect({
host: '127.0.0.1',
port: '8080',
username: 'username',
password: '******'
}).then(() => {
return sftp.list('/pathname');
}).then(data => {
console.log(data, 'the data info');
}).catch(err => {
console.log(err, 'catch error');
});
There has been minor changes to the API signatures
-
The
connect()
method no longer accepts a 'connectMethod' argument. It was not clear what this argument was for or what it did. -
Additional options are now available in the configure object passed to the
connect()
method to control the connection retry functionality. -
Node versions before 8.x are no longer supported.
-
Error message formats have changed. While they are now more consistent, if you have code which parses the messages, it will need to be updated.
-
The
auxList()
method is deprecated. An additional optionalpattern
argument has been added to thelist()
method to facilitate filtering of results returned bylist()
. Both 'glob' and regexp pattern styles are supported. -
The properties returned by the
stat()
method have changed. Thepermissions
property has been removed as it contained the same information as themode
property. New propertiesisDirectory
,isFile
,isBlockDevice
,isCharacterDevice
,isSymbolicLink
,isFIFO
andisSocket
have been added.
- Added ability to set a client name in
Client()
constructor. This can be useful when creating multiple clients as the client name will be displayed in error messages, providing a clue as to which client has failed. - Added a work-around for the SSH2 bug which results in only an
end
event being raised when the remote server drops the connection during the connect process. (see FAQ section below). - Added additional error checking to prevent attempts to call
connect()
on an already connected client. While a client can be used to make multiple connections, you must callend()
before callingconnect()
again. Each client object can only represent a single connection to an SFTP server. However, some methods, such asfastPut()
andfastGet()
will use concurrency to speed up the transfer of data. - Added some more examples in the example directory of the repository
- Some of the data upload/download methods would create an empty destination file when the source file did not exist. This has now been fixed.
- Handling of relative path names was weak and inconsistent. This has now been
made more consistent and reliable. Two new methods
realPath()
andcwd()
have been added - More error checking and provision of error messages with more meaningful information. Expansion and enhancements of test cases.
The connection options are the same as those offered by the underlying SSH2 module. For full details, please see SSH2 client methods
All the methods will return a Promise, except for on()
and
removeListener()
, which are typically only used in special use cases.
Constructor to create a new ssh2-sftp-client
object. An optional name
string
can be provided, which will be used in error messages to help identify which
client has thrown the error.
-
Constructor Arguments
- name: string. An optional name string used in error messages
-
Example Use
'use strict'; const Client = require('ssh2-sftp-client'); const config = { host: 'example.com', username: 'donald', password: 'my-secret' }; const sftp = new Client('example-client'); sftp.connect(config) .then(() => { return sftp.cwd(); }) .then(p => { console.log(`Remote working directory is ${p}`); return sftp.end(); }) .catch(err => { console.log(`Error: ${err.message}`); // error message will include 'example-client' });
Connect to an sftp server. Full documentation for connection options is available here
-
Connection Options
This module is based on the excellent SSH2 module. That module is a general SSH2 client and server library and provides much more functionality than just SFTP connectivity. Many of the connect options provided by that module are less relevant for SFTP connections. It is recommended you keep the config options to the minimum needed and stick to the options listed in the
commonOpts
below.The
retries
,retry_factor
andretry_minTimeout
options are not part of the SSH2 module. These are part of the configuration for the retry package and what is used to enable retrying of sftp connection attempts. See the documentation for that package for an explanation of these values.// common options let commonOpts { host: 'localhost', // string Hostname or IP of server. port: 22, // Port number of the server. forceIPv4: false, // boolean (optional) Only connect via IPv4 address forceIPv6: false, // boolean (optional) Only connect via IPv6 address username: 'donald', // string Username for authentication. password: 'borsch', // string Password for password-based user authentication agent: process.env.SSH_AGENT, // string - Path to ssh-agent's UNIX socket privateKey: fs.readFileSync('/path/to/key'), // Buffer or string that contains passphrase; 'a pass phrase', // string - For an encrypted private key readyTimeout: 20000, // integer How long (in ms) to wait for the SSH handshake strictVendor: true // boolean - Performs a strict server vendor check debug: myDebug // function - Set this to a function that receives a single // string argument to get detailed (local) debug information. retries: 2 // integer. Number of times to retry connecting retry_factor: 2 // integer. Time factor used to calculate time between retries retry_minTimeout: 2000 // integer. Minimum timeout between attempts }; // rarely used options let advancedOpts { localAddress, localPort, hostHash, hostVerifier, agentForward, localHostname, localUsername, tryKeyboard, authHandler, keepaliveInterval, keepaliveCountMax, sock, algorithms, compress };
-
Example Use
sftp.connect({ host: example.com, port: 22, username: 'donald', password: 'youarefired' });
Retrieves a directory listing. This method returns a Promise, which once realised, returns an array of objects representing items in the remote directory.
- path: {String} Remote directory path
- pattern: (optional) {string|RegExp} A pattern used to filter the items included in the returned
array. Pattern can be a simple glob-style string or a regular
expression. Defaults to
/.*/
.
-
Example Use
const Client = require('ssh2-sftp-client'); const config = { host: 'example.com', port: 22, username: 'red-don', password: 'my-secret' }; let sftp = new Client; sftp.connect(config) .then(() => { return sftp.list('/path/to/remote/dir'); }) .then(data => { console.log(data); }) .then(() => { sftp.end(); }) .catch(err => { console.error(err.message); });
-
Return Objects
The objects in the array returned by
list()
have the following properties;{ type: // file type(-, d, l) name: // file name size: // file size modifyTime: // file timestamp of modified time accessTime: // file timestamp of access time rights: { user: group: other: }, owner: // user ID group: // group ID }
-
Pattern Filter
The filter options can be a regular expression (most powerful option) or a simple glob-like string where * will match any number of characters, e.g.
foo* => foo, foobar, foobaz *bar => bar, foobar, tabbar *oo* => foo, foobar, look, book
The glob-style matching is very simple. In most cases, you are best off using a real regular expression which will allow you to do more powerful matching and anchor matches to the beginning/end of the string etc.
Tests to see if remote file or directory exists. Returns type of remote object if it exists or false if it does not.
-
Example Use
const Client = require('ssh2-sftp-client'); const config = { host: 'example.com', port: 22, username: 'red-don', password: 'my-secret' }; let sftp = new Client; sftp.connect(config) .then(() => { return sftp.exists('/path/to/remote/dir'); }) .then(data => { console.log(data); // will be false or d, -, l (dir, file or link) }) .then(() => { sftp.end(); }) .catch(err => { console.error(err.message); });
Returns the attributes associated with the object pointed to by path
.
- path: String. Remote path to directory or file on remote server
-
Attributes
The
stat()
method returns an object with the following properties;let stats = { mode: 33279, // integer representing type and permissions uid: 1000, // user ID gid: 985, // group ID size: 5, // file size accessTime: 1566868566000, // Last access time. milliseconds modifyTime: 1566868566000, // last modify time. milliseconds isDirectory: false, // true if object is a directory isFile: true, // true if object is a file isBlockDevice: false, // true if object is a block device isCharacterDevice: false, // true if object is a character device isSymbolicLink: false, // true if object is a symbolic link isFIFO: false, // true if object is a FIFO isSocket: false // true if object is a socket };
-
Example Use
let client = new Client(); client.connect(config) .then(() => { return client.stat('/path/to/remote/file'); }) .then(data => { // do something with data }) .then(() => { client.end(); }) .catch(err => { console.error(err.message); });
Retrieve a file from a remote SFTP server. The dst
argument defines the
destination and can be either a string, a writeable stream or undefined. If it
is a string, it is interpreted as the path to a location on the local file
system (path should include the file name). If it is a writeable stream, the
remote data is piped into that stream. If dst
is undefined, the method will
put the data into a buffer and return that buffer when the Promise is
resolved. If dst
is defined, it is returned when the Promise is resolved.
In general, if your going to pass in a string as the destination, you are
probably better off using the fastGet()
method.
- path: String. Path to the remote file to download
- dst: String|Stream. Destination for the data. If a string, it should be a local file path.
- options: Options for the
get()
command (see below).
-
Options
The options object can be used to pass options to the underlying readStream used to read the data from the remote server.
{ flags: 'r', encoding: null, handle: null, mode: 0o666, autoClose: true }
Most of the time, you won't want to use any options. Sometimes, it may be useful to set the encoding. For example, to 'utf-8'. However, it is important not to do this for binary files to avoid data corruption.
-
Example Use
let client = new Client(); let remotePath = '/remote/server/path/file.txt'; let dst = fs.createWriteStream('/local/file/path/copy.txt'); client.connect(config) .then(() => { return client.get(remotePath, dst); }) .then(() => { client.end(); }) .catch(err => { console.error(err.message); });
- Tip: See examples file in the Git repository for more examples. You can pass
any writeable stream in as the destination. For example, if you pass in
zlib.createGunzip()
writeable stream, you can both download and decompress a gzip file 'on the fly'.
- Tip: See examples file in the Git repository for more examples. You can pass
any writeable stream in as the destination. For example, if you pass in
Downloads a file at remotePath to localPath using parallel reads for faster throughput. This is the simplest method if you just want to download a file.
- remotePath: String. Path to the remote file to download
- localPath: String. Path on local file system for the downloaded file. The local path should include the filename to use for saving the file.
- options: Options for
fastGet()
(see below)
-
Options
{ concurrency: 64, // integer. Number of concurrent reads to use chunkSize: 32768, // integer. Size of each read in bytes step: function(total_transferred, chunk, total) // callback called each time a // chunk is transferred }
- Warning: Some servers do not respond correctly to requests to alter chunk size. This can result in lost or corrupted data.
-
Sample Use
let client = new Client(); let remotePath = '/server/path/file.txt'; let localPath = '/local/path/file.txt'; client.connect(config) .then(() => { client.fastGet(remotePath, localPath); }) .then(() => { client.end(); }) .catch(err => { console.error(err.message); });
Upload data from local system to remote server. If the src
argument is a
string, it is interpreted as a local file path to be used for the data to
transfer. If the src
argument is a buffer, the contents of the buffer are
copied to the remote file and if it is a readable stream, the contents of that
stream are piped to the remotePath
on the server.
- src: string | buffer | readable stream. Data source for data to copy to the remote server.
- remotePath: string. Path to the remote file to be created on the server.
- options: object. Options which can be passed to adjust the write stream used in sending the data to the remote server (see below).
-
Options
The following options are supported;
{ flags: 'w', // w - write and a - append encoding: null, // use null for binary files mode: 0o666, // mode to use for created file (rwx) autoClose: true // automatically close the write stream when finished }
The most common options to use are mode and encoding. The values shown above are the defaults. You do not have to set encoding to utf-8 for text files, null is fine for all file types. However, using utf-8 encoding for binary files will often result in data corruption.
-
Example Use
let client = new Client(); let data = fs.createReadStream('/path/to/local/file.txt'); let remote = '/path/to/remote/file.txt'; client.connect(config) .then(() => { return client.put(data, remote); }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
- Tip: If the src argument is a path string, consider just using
fastPut()
.
- Tip: If the src argument is a path string, consider just using
Uploads the data in file at localPath
to a new file on remote server at
remotePath
using concurrency. The options object allows tweaking of the fast put process.
- localPath: string. Path to local file to upload
- remotePath: string. Path to remote file to create
- options: object. Options passed to createWriteStream (see below)
-
Options
{ concurrency: 64, // integer. Number of concurrent reads chunkSize: 32768, // integer. Size of each read in bytes mode: 0o755, // mixed. Integer or string representing the file mode to set step: function(total_transferred, chunk, total) // function. Called every time // a part of a file was transferred }
- Warning: There have been reports that some SFTP servers will not honour requests for non-default chunk sizes. This can result in data loss or corruption.
-
Example Use
let localFile = '/path/to/file.txt'; let remoteFile = '/path/to/remote/file.txt'; let client = new Client(); client.connect(config) .then(() => { client.fastPut(localFile, remoteFile); }) .then(() => { client.end(); }) .catch(err => { console.error(err.message); });
Append the input
data to an existing remote file. There is no integrity
checking performed apart from normal writeStream checks. This function simply
opens a writeStream on the remote file in append mode and writes the data passed
in to the file.
- input: buffer | readStream. Data to append to remote file
- remotePath: string. Path to remote file
- options: object. Options to pass to writeStream (see below)
-
Options
The following options are supported;
{ flags: 'a', // w - write and a - append encoding: null, // use null for binary files mode: 0o666, // mode to use for created file (rwx) autoClose: true // automatically close the write stream when finished }
The most common options to use are mode and encoding. The values shown above are the defaults. You do not have to set encoding to utf-8 for text files, null is fine for all file types. Generally, I would not attempt to append binary files.
-
Example Use
let remotePath = '/path/to/remote/file.txt'; let client = new Client(); client.connect(config) .then(() => { return client.append(Buffer.from('Hello world'), remotePath); }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
Create a new directory. If the recursive flag is set to true, the method will create any directories in the path which do not already exist. Recursive flag defaults to false.
- path: string. Path to remote directory to create
- recursive: boolean. If true, create any missing directories in the path as well
-
Example Use
let remoteDir = '/path/to/new/dir'; let client = new Client(); client.connect(config) .then(() => { return client.mkdir(remoteDir, true); }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
Remove a directory. If removing a directory and recursive flag is set to
true
, the specified directory and all sub-directories and files will be
deleted. If set to false and the directory has sub-directories or files, the
action will fail.
- path: string. Path to remote directory
- recursive: boolean. If true, remove all files and directories in target directory. Defaults to false
-
Example Use
let remoteDir = '/path/to/remote/dir'; let client = new Client(); client.connect(config) .then(() => { return client.rmdir(remoteDir, true); }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
Delete a file on the remote server.
- path: string. Path to remote file to be deleted.
-
Example Use
let remoteFile = '/path/to/remote/file.txt'; let client = new Client(); client.connect(config) .then(() => { return client.delete(remoteFile); }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
Rename a file or directory from fromPath
to toPath
. You must have the
necessary permissions to modify the remote file.
-
Example Use
let from = '/remote/path/to/old.txt'; let to = '/remote/path/to/new.txt'; let client = new Client(); client.connect(config) .then(() => { return client.rename(from, to); }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
Change the mode (read, write or execute permissions) of a remote file or directory.
- path: string. Path to the remote file or directory
- mode: octal. New mode to set for the remote file or directory
-
Example Use
let path = '/path/to/remote/file.txt'; let ndwMode = 0o644; // rw-r-r let client = new Client(); client.connect(config) .then(() => { return client.chmod(path, newMode); }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
Converts a relative path to an absolute path on the remote server. This method is mainly used internally to resolve remote path names.
- path: A file path, either relative or absolute
Returns what the server believes is the current remote working directory.
Ends the current client session, releasing the client socket and associated resources. This function also removes all listeners associated with the client.
-
Example Use
let client = new Client(); client.connect(config) .then(() => { // do some sftp stuff }) .then(() => { return client.end(); }) .catch(err => { console.error(err.message); });
Although normally not required, you can add and remove custom listeners on the ssh2 client object. This object supports a number of events, but only a few of them have any meaning in the context of SFTP. These are
- error: An error occurred. Calls listener with an error argument.
- end: The socket has been disconnected. No argument.
- close: The socket was closed. Boolean argument which is true when the socket was closed due to errors.
-
on(eventType, listener)
Adds the specified listener to the specified event type. It the event type is
error
, the listener should accept 1 argument, which will be an Error object. If the event type isclose
, the listener should accept one argument of a boolean type, which will be true when the client connection was closed due to errors. -
removeListener(eventType, listener)
Removes the specified listener from the event specified in eventType. Note that the
end()
method automatically removes all listeners from the client object.
Many SFTP servers have rate limiting protection which will drop connections once
a limit has been reached. In particular, openSSH has the setting MaxStartups
,
which can be a tuple of the form max:drop:full
where max
is the maximum
allowed unauthenticated connections, drop
is a percentage value which
specifies percentage of connections to be dropped once max
connections has
been reached and full
is the number of connections at which point all
subsequent connections will be dropped. e.g. 10:30:60
means allow up to 10
unauthenticated connections after which drop 30% of connection attempts until
reaching 60 unauthenticated connections, at which time, drop all attempts.
Clients first make an unauthenticated connection to the SFTP server to begin
negotiation of protocol settings (cipher, authentication method etc). If you are
creating multiple connections in a script, it is easy to exceed the limit,
resulting in some connections being dropped. As SSH2 only raises an 'end' event
for these dropped connections, no error is detected. The ssh2-sftp-client
now
listens for end
events during the connection process and if one is detected,
will reject the connection promise.
One way to avoid this type of issue is to add a delay between connection
attempts. It does not need to be a very long delay - just sufficient to permit
the previous connection to be authenticated. In fact, the default setting for
openSSH is 10:30:60
, so you really just need to have enough delay to ensure
that the 1st connection has completed authentication before the 11th connection
is attempted.
If the dst argument passed to the get method is a writeable stream, the remote
file will be piped into that writeable. If the writeable you pass in is a
writeable stream created with fs.createWriteStream()
, the data will be written
to the file specified in the constructor call to createWriteStream()
.
The writeable stream can be any type of write stream. For example, the below code
will convert all the characters in the remote file to upper case before it is
saved to the local file system. This could just as easily be something like a
gunzip stream from zlib
, enabling you to decompress remote zipped files as you
bring them across before saving to local file system.
'use strict';
// Example of using a writeable with get to retrieve a file.
// This code will read the remote file, convert all characters to upper case
// and then save it to a local file
const Client = require('../src/index.js');
const path = require('path');
const fs = require('fs');
const through = require('through2');
const config = {
host: 'arch-vbox',
port: 22,
username: 'tim',
password: 'xxxx'
};
const sftp = new Client();
const remoteDir = '/home/tim/testServer';
function toupper() {
return through(function(buf, enc, next) {
next(null, buf.toString().toUpperCase());
});
}
sftp
.connect(config)
.then(() => {
return sftp.list(remoteDir);
})
.then(data => {
// list of files in testServer
console.dir(data);
let remoteFile = path.join(remoteDir, 'test.txt');
let upperWtr = toupper();
let fileWtr = fs.createWriteStream(path.join(__dirname, 'loud-text.txt'));
upperWtr.pipe(fileWtr);
return sftp.get(remoteFile, upperWtr);
})
.then(() => {
return sftp.end();
})
.catch(err => {
console.error(err.message);
});
There are a couple of ways to do this. Essentially, you want to setup SSH keys and use these for authentication to the remote server.
One solution, provided by @KalleVuorjoki is to use the SSH agent process. Note: SSHAUTHSOCK is normally created by your OS when you load the ssh-agent as part of the login session.
let sftp = new Client();
sftp.connect({
host: 'YOUR-HOST',
port: 'YOUR-PORT',
username: 'YOUR-USERNAME',
agent: process.env.SSH_AUTH_SOCK
}).then(() => {
sftp.fastPut(/* ... */)
}
Another alternative is to just pass in the SSH key directly as part of the configuration.
let sftp = new Client();
sftp.connect({
host: 'YOUR-HOST',
port: 'YOUR-PORT',
username: 'YOUR-USERNAME',
privateKey: fs.readFileSync('/path/to/ssh/key')
}).then(() => {
sftp.fastPut(/* ... */)
}
This solution was provided by @jmorino.
import { SocksClient } from 'socks';
import SFTPClient from 'ssh2-sftp-client';
const host = 'my-sftp-server.net';
const port = 22; // default SSH/SFTP port on remote server
// connect to SOCKS 5 proxy
const { socket } = await SocksClient.createConnection({
proxy: {
host: 'my.proxy', // proxy hostname
port: 1080, // proxy port
type: 5, // for SOCKS v5
},
command: 'connect',
destination: { host, port } // the remote SFTP server
});
const client = new SFTPClient();
client.connect({
host,
sock: socket, // pass the socket to proxy here (see ssh2 doc)
username: '.....',
privateKey: '.....'
})
// client is connected
- Fix bug in
exist()
where tests on root directory returned false - Minor documentation fixes
- Clean up mkdir example
- Minor documentation fixes
- Added additional examples in the
example
directory
- Remove default close listener. changes in ssh2 API removed the utility of a default close listener
- Fix path handling. Under mixed environments (where client platform and server platform were different i.e. one windows the other unix), path handling was broken due tot he use of path.join().
- Ensure error messages include path details. Instead of errors such as "No such file" now report "No such file /path/to/missing/file" to help with debugging
- Work-around for SSH2
end
event bug - Added ability to set client name in constructor method
- Added additional error checking to prevent
connect()
being called on already connected client - Added additional examples in
example
directory
- move
end()
call to resolve into close hook - Prevent
put()
andget()
from creating empty files in destination when unable to read source - Expand tests for operations when lacking required permissions
- Add additional data checks for
append()
- Verify file exists
- Verify file is writeable
- Verify file is a regular file
- Fix handling of relative paths
- Add
realPath()
method - Add
cwd()
method
- Minor documentation fix
- Fix return value from
get()
- Fix bug in mkdir() relating to handling of relative paths
- Modify exists() to always return 'd' if path is '.'
- Fix some minor packaging issues
- Remove support for node < 8.x
- Fix connection retry feature
- sftp connection object set to null when 'end' signal is raised
- Removed 'connectMethod' argument from connect method.
- Refined adding/removing of listeners in connect() and end() methods to enable errors to be adequately caught and reported.
- Deprecate auxList() and add pattern/regexp filter option to list()
- Refactored handling of event signals to provide better feedback to clients
- Removed pointless 'permissions' property from objects returned by
stat()
(same as mode property). Added additional properties describing the type of object. - Added the
removeListener()
method to compliment the existingon()
method.
- Repository transferred to theophilusx
- Fix error in package.json pointing to wrong repository
- Apply 4 pull requests to address minor issues prior to transfer
- ???
- merge #108, #110
- fix connect promise if connection ends
- merge #105
- fix windows path
- merge pr #99, #100
- bug fix
- Requires node.js v7.5.0 or above.
- merge pr #97, thanks for @theophilusx
- Remove emitter.maxListener warnings
- Upgraded ssh2 dependency from 0.5.5 to 0.6.1
- Enhanced error messages to provide more context and to be more consistent
- re-factored test
- Added new 'exists' method and re-factored mkdir/rmdir
- add:
stat
method - add
fastGet
andfastPut
method. - fix:
mkdir
file exists decision logic
- change:
sftp.get
will return chunk not stream anymore - fix: get readable not emitting data events in node 10.0.0
- add:
chmod
method pr#33 - update: upgrade ssh2 to V0.5.0 pr#30
- fix: get method stream error reject unwork #22
- fix: return Error object on promise rejection pr#20
- fix: add encoding control support for binary stream
- fix: multi image upload
- change: remove
this.client.sftp
toconnect
function
Please log an issue for all bugs, questions, feature and enhancement requests. Please ensure you include the module version, node version and platform.
Pull requests are always welcomed. However, please ensure your changes pass all tests and if your adding a new feature, that tests for that feature are included. Likewise, for new features or enhancements, please include any relevant documentation updates.
This module will adopt a standard semantic versioning policy. Please indicate in your pull request what level of change it represents i.e.
- Major: Change to API or major change in functionality which will require an increase in major version number.
- Minor: Minor change, enhancement or new feature which does not change existing API and will not break existing client code.
- Bug Fix: No change to functionality or features. Simple fix of an existing bug.
This module was initially written by jyu213. On August 23rd, 2019, theophilusx took over responsibility for maintaining this module. A number of other people have contributed to this module, but until now, this was not tracked. My intention is to credit anyone who contributes going forward.
- jyu213: Original author
- theophilusx: Current maintainer
- henrytk: Documentation fix
- waldyrious: Documentation fixes