electerious / nice-try

Tries to execute a function and discards any error that occurs.

nice-try

A function that tries to execute a function and discards any error that occurs.

Install

npm install nice-try

Usage

const niceTry = require('nice-try')

niceTry(() => JSON.parse('true')) // true
niceTry(() => JSON.parse('truee')) // undefined
niceTry() // undefined
niceTry(true) // undefined

await niceTry.promise(async () => JSON.parse('true')) // true
await niceTry.promise(async () => JSON.parse('truee')) // undefined

API

Parameters

• fn {Function} Function that might or might not throw an error.

Returns

• {?*} Return-value of the function when no error occurred.

What others say

This module is a controversial thing and people like to get mad about it. I decided to give those people a voice. Here's what they're saying.

fundamentally inane

— frou_dh

the worst Javascript library […] in several categories

— kuzux

how is this a thing

— uint8_t

This is blowing my mind

— mr_jim_lahey

a shit-tastic try-catch alias

— Dropping_fruits

I assumed every commit was a joke, but after researching the maintainer a bit I'm not sure it is...

— MrPineappleHat

nice-try's Issues

Nice try

An in-range update of coveralls is breaking the build 🚨

The devDependency coveralls was updated from 3.0.5 to 3.0.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/coveralls-3.0.6 at 100.0% (Details).

---

Commits

The new version differs by 3 commits.

• 1e09691 Merge branch 'master' of https://github.com/nickmerwin/node-coveralls
• d3045b4 handleInput callback include body
• e55883a COVERALLS_PARALLEL docs link update

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Why?

Why would anyone use this?

Add support for C#

Hello,

I was wondering if you would be willing to port this package to C#? It seems like it would be a good addition to the repository.

Types for TypeScript?

nice-try doesn't work with TypeScript because of lack of types

Support for IE5?

Support for Internet Explorer 5?

Promise support

It would be useful if nice-try supported promises:

const niceTry = require('nice-try')

const result = await niceTry.promise(async () => {...})

Implementation:

module.exports.promise = async function(fn) {

	try { return await fn() } catch (e) {}

}

// @electerious

How about hi-order?

High-order counterpart:

var niceTry = require('nice-try/method')
var parse = niceTry((...args) => JSON.parse(...args))
// or
var parse = niceTry(JSON.parse)
// then
var value = parse('true')

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Support for C++?

Hi, thanks for the project!

I’m wondering if you can provide bindings to also support nicely trying C++ functions? I find it harder to try/catch those, especially exceptions like OOM.