babel-plugin-better-async-await
v1.1.1
Published
babel plugin for better error handling using async await
Downloads
5
Maintainers
Readme
babel-plugin-better-async-await
Write better async await and avoid the try catch statements This plugin works well if the following preset is used better-async-await.
💡For usage with CRA and any app which relies on @babel/env or on ordering of presets and plugins, we would highly recommend using better-async-await.macro
NOTE: If you are using babel-preset-env, default CRA config or @babel/env or babel-plugin-transform-async-to-generator, then the order of presets matter and this plugin can not be used.
🚚 Installation
npm install --save-dev babel-preset-better-async-await
or
yarn add babel-preset-better-async-await --dev
Motivation and Idea
This babel plugin is inspired from the idea of this post https://blog.grossman.io/how-to-write-async-await-without-try-catch-blocks-in-javascript/ written by - Dima Grossman
In async/await functions we often use try/catch blocks to catch errors.
For example:-
async function completeApplicationFlow() {
// wait for get session status api to check the status
let response;
try {
response = await getSessionStatusApi();
} catch(err) {
// if error show a generic error message
return handleError(err);
}
// wait for getting next set of questions api
try {
response = await getNextQuestionsApi();
} catch(err) {
// if error show a generic error message
return handleError(err);
}
// finally submit application
try {
response = await submitApplication();
} catch(err) {
// if error show a generic error message
return handleError(err);
}
}
Approach inspired from the blog and a different way of doing this could be:-
async function completeApplicationFlow() {
// wait for get session status api to check the status
let err, response;
// wait for get session status api to check the status
[err, response] = await getSessionStatusApi();
// if error show a generic error message
if (err) return handleError(err);
// call getNextQuestion Api
[err, response] = await getNextQuestionsApi();
// if error show a generic error message
if (err) return handleError(err);
// finally submit application
[err, response] = this.submitApplication();
if (err) return handleError(err);
}
⚡️ The problem solved
Using this babel preset you could write async await in the alternate approach mentioned above. We will transform your async await code so that it works the
[err, resp]
way.
📒 Examples of using it in your code
Before
async function test() {
let resp;
try {
resp = await api.getData(5);
} catch(err)
handleError();
}
}
After
async function test() {
const [err, resp] = await api.getData(5);
if(err) handleError();
// else do something with the response
}
Before
async function test() {
let resp;
try {
resp = await getData;
} catch(err)
handleError();
}
}
function getData() {
return new Promise((resolve, reject) => {
setTimeout(() => {
resolve(true);
}, 1000);
});
}
After
async function test() {
const [err, resp] = await getData
if(err) handleError();
// else do something with the response
}
function getData() {
return new Promise((resolve, reject) => {
setTimeout(() => {
resolve(true);
}, 1000);
});
}
Before
async function test() {
let resp;
try {
resp = await fetch('http://some-rest-endpoint');
} catch(err)
handleError();
}
}
After
async function test() {
const [err, resp] = await fetch('http://some-rest-endpoint');
if(err) handleError();
// else do something with the response
}
📒 Babel Tranformation
In
async function test() {
const [err, resp] = await fetch('http://some-rest-endpoint');
}
Out
async function test() {
const [err, resp] = await fetch('http://some-rest-endpoint').then(resp => {
return [null, resp];
}).catch(error => {
return [error];
})
}
⭐ Usage
Via .babelrc
(Recommended) without options
.babelrc
{
"presets": ["better-async-await"]
}
NOTE: If you are using babel-preset-env, default CRA config or @babel/env or babel-plugin-transform-async-to-generator, then the order of presets matter and this plugin can not be used.
Via CLI
babel --presets better-async-await script.js
NOTE: If you are using babel-preset-env, default CRA config or @babel/env or babel-plugin-transform-async-to-generator, then the order of presets matter and this plugin can not be used.
Via Node API
require('babel-core').transform('code', {
presets: [
'better-async-await',
],
});
NOTE: If you are using babel-preset-env, default CRA config or @babel/env or babel-plugin-transform-async-to-generator, then the order of presets matter and this plugin can not be used.
👍 Contribute
Show your ❤️ and support by giving a ⭐. Any suggestions and pull request are welcome !
📝 License
MIT © viveknayyar
👷 TODO
- [x] Complete README
- [ ] Add Examples and Demo
- [x] Test Suite
Contributors
Thanks goes to these wonderful people (emoji key):
| Vivek Nayyar🐛 💻 🎨 📖 💡 🤔 📦 🔌 ⚠️ 🔧 ✅ | | :---: |
This project follows the all-contributors specification. Contributions of any kind welcome!