Skip to content

issues Search Results · repo:JS-DevTools/ono language:JavaScript

Filter by

14 results
 (69 ms)

14 results

inJS-DevTools/ono (press backspace or delete to remove)

https://github.com/JS-DevTools/ono/blob/a1fa89a25e7432f7615af8b4179f842b5affccf2/src/index.ts#L10-L13 This code block is bombing my rollup build. Not caught during build. This code makes it into the bundle, ...
  • Prophet32j
  • 1
  • Opened 
    on May 17, 2023
  • #19

Description I ve detected problematic usage of source maps from @jsdevtools/ono@7.1.3. Issue is manifesting when using for example Create React App to build the application using @jsdevtools/ono@7.1.3 ...
  • char0n
  • Opened 
    on Jan 10, 2022
  • #18

Importing inspect form utils isn t supported in vite. This project is imported by some other projects and it breaks the build. Is it possible to remove the import?
  • cperrin88
  • 2
  • Opened 
    on Dec 7, 2021
  • #17

Hiya, thank you for this great library! I was wondering if this is possible to do today or if it could be implemented as an enhancement? Right now the stack trace is only preserved for the original error, ...
  • petermetz
  • Opened 
    on May 26, 2021
  • #16

I see that the toJSON is deliberately used for the Symbol.for( nodejs.util.inspect.custom ) custom formatter. This doesn t feel very conducive to clear and concise error messages. Take the following for ...
  • ferm10n
  • Opened 
    on Oct 12, 2020
  • #15

npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@jsdevtools%2fono - Not found npm ERR! 404 npm ERR! 404 @jsdevtools/ono@^7.1.3 is not in the npm registry. npm ERR! 404 You should ...
  • AlexandrKoliukh
  • 1
  • Opened 
    on Aug 6, 2020
  • #14

I installed the recent version of ono (7.1.2) using npm and received the following error ERROR in ../node_modules/@jsdevtools/ono/esm/types.d.ts:135:5 - error TS1169: A computed property name in an interface ...
more info needed
  • KirillGordineRhenag
  • 4
  • Opened 
    on Jun 4, 2020
  • #13

Is there a way to wrap an error so that the instance/prototype of the original error is not lost? This makes it easy to catch up the stack using instanceof calls or decorators that rely on using the class ...
question
  • ryanleecode
  • 5
  • Opened 
    on May 12, 2020
  • #12

Hey! I have a case in my API project when I want to catch an error from some 3-d party library/ies and re-throw an ono error with original error as an inner error. Because 3-d library/ies can throw any ...
enhancement
  • PizzaPartyInc
  • 3
  • Opened 
    on Nov 22, 2019
  • #11

I could swear this was working earlier this year, but after upgrading to latest node / types / webpack, simply importing or requiring isomorphic.node triggers a runtime error Cannot read property inspect ...
more info needed
  • pcafstockf
  • 4
  • Opened 
    on Oct 8, 2019
  • #9
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