Skip to content

issues Search Results · repo:browserify/parse-asn1 language:JavaScript

Filter by

20 results
 (87 ms)

20 results

inbrowserify/parse-asn1 (press backspace or delete to remove)

browserify/parse-asn1
asn.define is not a function

Cannot use browserify-sign because of this problem Image
  • Sleep1ngosu
  • 3
  • Opened 
    on Oct 22, 2024
  • #48

browserify/parse-asn1
Error

This is using an outdated version asn1.js where there is an error Can t resolve vm in \node_modules\parse-asn1\node_modules\asn1.js\lib\asn1
  • lcalhoun-scs
  • 5
  • Opened 
    on Aug 28, 2024
  • #47

browserify/parse-asn1
"Module not found" in latest release (5.1.7)

Can t build the app anymore after your last release: Module not found: Error: Can t resolve vm in ~/app/node_modules/asn1.js/lib/asn1 @ ./node_modules/asn1.js/lib/asn1.js 5:14-42 @ ./node_modules/parse-asn1/asn1.js ...
  • VasylBoyko
  • 8
  • Opened 
    on Mar 13, 2024
  • #46

browserify/parse-asn1
"asn1.js": "^5.2.0" with error

SyntaxError: Use of const in strict mode.
  • lazybusy
  • 5
  • Opened 
    on Aug 19, 2020
  • #45

browserify/parse-asn1
v5.1.6 introduces breaking change

update of asn1 in #37 introduces breaking change You can see that CI is failing since that change: https://github.com/crypto-browserify/parse-asn1/commits/v5.1.6 although that failure doesn t appear to ...
  • mjacksonest
  • 14
  • Opened 
    on Aug 12, 2020
  • #41

browserify/parse-asn1
Upgrade asn1.js to ^5.2.0

The usage of eval was removed from asn1.js a few days ago (https://github.com/indutny/asn1.js/issues/108) but parse-asn1 still depends on asn1.js@4. Could it be bumped to the latest version?
  • voluntadpear
  • 8
  • Opened 
    on Oct 9, 2019
  • #39

browserify/parse-asn1
fixProc startRegex "PUBLIC KEY"

fixProc.js line 25 var tag = key.match(startRegex)[1] does not return PUBLIC KEY because the startRegex fails. See https://regex101.com/ for example. Enter the startRegex: /^-----BEGIN ((?:.* KEY)|CERTIFICATE)-----/m, ...
  • CarstenHouweling
  • 2
  • Opened 
    on Feb 8, 2019
  • #35

browserify/parse-asn1
Unexpected token: keyword (const)

This is the output of uglifyjs from last build, we should replace const to var in index.js
  • mufasa71
  • Opened 
    on Jan 17, 2019
  • #33

browserify/parse-asn1
Failing to parse certificates

The following lines fail: var parseKeys = require( parse-asn1 ) key = `-----BEGIN CERTIFICATE----- MIIDUDCCAjgCCQD1TryolF9FbDANBgkqhkiG9w0BAQsFADBzMQswCQYDVQQGEwJV UzEOMAwGA1UECAwFVGV4YXMxDzANBgNVBAcMBkRhbGxhczEWMBQGA1UECgwNUHVi ...
  • Benhawkins18
  • 1
  • Opened 
    on Jan 15, 2019
  • #31

browserify/parse-asn1
Buffer constructor runtime deprecation - this package emits a warning on Node 10

Hey, Starting on Node 10 this package will emit deprecation warnings. See this guide on what you should do in order to migrate to Buffer.alloc/Buffer.from. See https://github.com/nodejs/node/issues/19079 ...
  • benjamingr
  • 1
  • Opened 
    on Mar 20, 2018
  • #29
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub