jshttp/range-parser issues and pull requests

#27 - add OSSF scorecard action

Pull Request - State: closed - Opened by carpasse 6 months ago

#26 - Fix and upgrade ci pipeline

Pull Request - State: closed - Opened by carpasse 6 months ago - 3 comments

#25 - return -2 when start or end is specified but not a number. fixes #24

Pull Request - State: closed - Opened by mreinstein about 2 years ago - 6 comments
Labels: bug, pr

#24 - invalid start and end byte ranges should return -2

Issue - State: open - Opened by mreinstein about 2 years ago - 4 comments
Labels: bug

#23 - the `size` parameter should probably be optional

Issue - State: closed - Opened by mreinstein about 2 years ago - 1 comment
Labels: ideas

#22 - rangeParser is not a function

Issue - State: closed - Opened by digimbyte almost 3 years ago - 5 comments
Labels: question

#21 - Does this work in a browser environment?

Issue - State: closed - Opened by PierBover about 3 years ago - 1 comment
Labels: question

#20 - Update index.js

Pull Request - State: closed - Opened by faizanu94 over 3 years ago - 1 comment
Labels: pr

#19 - Why is the last-byte-pos set to the size when a requested part's end is after the maximum size of the resource?

Issue - State: closed - Opened by sammbeller over 5 years ago - 8 comments
Labels: question

#18 - Add max size on open range

Pull Request - State: closed - Opened by Meettya about 6 years ago - 6 comments
Labels: pr

#17 - Export `combineRanges()` function

Pull Request - State: open - Opened by piranna over 6 years ago - 1 comment
Labels: pr, needs tests, needs docs

#16 - Why is size required

Issue - State: closed - Opened by nicolasroger17 about 7 years ago - 2 comments
Labels: question

#15 - Combine overlapping ranges

Pull Request - State: closed - Opened by jcready over 8 years ago - 5 comments
Labels: enhancement, pr

#14 - Valid if ANY of the range-specifier values overlap

Pull Request - State: closed - Opened by jcready over 8 years ago - 16 comments
Labels: pr

#13 - A range request is valid if ANY of the range-specifier values overlap the representation

Issue - State: closed - Opened by jcready over 8 years ago

#12 - Check module node.js 4.* to raise in express.js

Pull Request - State: closed - Opened by nook-scheel about 9 years ago
Labels: pr

#11 - Range: bytes=0-

Issue - State: closed - Opened by elebescond over 9 years ago - 3 comments

#10 - parser: less isNaN checks

Pull Request - State: closed - Opened by Fishrock123 about 10 years ago - 1 comment

#9 - Rename to range-parser

Issue - State: closed - Opened by Fishrock123 about 10 years ago - 2 comments

#8 - move to expressjs org or add me as maintainer

Issue - State: closed - Opened by jonathanong over 10 years ago

#7 - add repo field

Issue - State: closed - Opened by jonathanong almost 11 years ago - 1 comment

#6 - Support range unit ?

Issue - State: closed - Opened by redben about 11 years ago - 5 comments
Labels: enhancement

#5 - please push git tag 0.0.4

Issue - State: closed - Opened by kapouer about 11 years ago - 4 comments

#4 - Added license type and reference to LICENSE file to the package.json

Pull Request - State: closed - Opened by zubairov about 11 years ago

#3 - added repository to package.json

Pull Request - State: closed - Opened by redchair123 over 11 years ago

#2 - add repo to package.json

Issue - State: closed - Opened by redchair123 over 11 years ago - 3 comments

#1 - Include test/ in npm tarball

Pull Request - State: closed - Opened by jamielinux over 11 years ago - 2 comments

Ecosyste.ms: Issues

GitHub / jshttp/range-parser issues and pull requests