libreccm-legacy/trunk-images/node_modules/remove-trailing-separator
baka a212bb7b37 [3056] Adds Plugin to add Images from the system in tinymce. Now with files...
git-svn-id: https://svn.libreccm.org/ccm/trunk@5722 8810af33-2d31-482b-a856-94f89814c4df
2018-11-03 23:44:15 +00:00
..
history.md [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
index.js [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
license [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
package.json [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00
readme.md [3056] Adds Plugin to add Images from the system in tinymce. Now with files... 2018-11-03 23:44:15 +00:00

readme.md

remove-trailing-separator

NPM version Build Status: Linux Build Status: Windows Coverage Status

Removes all separators from the end of a string.

Install

npm install remove-trailing-separator

Examples

const removeTrailingSeparator = require('remove-trailing-separator');

removeTrailingSeparator('/foo/bar/')   // '/foo/bar'
removeTrailingSeparator('/foo/bar///') // '/foo/bar'

// leaves only/last separator
removeTrailingSeparator('/')    // '/'
removeTrailingSeparator('///')  // '/'

// returns empty string
removeTrailingSeparator('') // ''

Notable backslash, or win32 separator behavior

\ is considered a separator only on WIN32 systems. All POSIX compliant systems see backslash as a valid file name character, so it would break POSIX compliance to remove it there.

In practice, this means that this code will return different things depending on what system it runs on:

removeTrailingSeparator('\\foo\\')
// UNIX  => '\\foo\\'
// WIN32 => '\\foo'