No need to use body-parser when using express version 4.16+

[abhay27chauhan]

Proposal

Express version 4.16+, their own body-parser implementation is now included in the default Express package so there is no need for you to download another dependency.

You have added a line to your code that looks like the following:

• app.use(bodyParser.urlencoded({extended: true}));

If you are using Express 4.16+ you can now replace that line with:

• app.use(express.urlencoded());

[abhay27chauhan]

I am a participant of GSSOC21, so please let me know if this is a valid proposal

[github-actions[bot]]

Hi, thanks for creating your first issue at BlogSite, do read and follow the Code of Conduct and the Contribution Guidelines while contributing.

[Pranav016]

I agree with you but I think there is no harm in having that package because right now its working fine in production, without out it might or might not.. Closing issue for now, reopen if required.

[Pranav016]

/reviewed

[abhay27chauhan]

Because now it is inbuilt in express so no need to Install additional dependency and in vs code also it gives warning if you use bodyparser

On Sat, 13 Mar, 2021, 2:49 PM Pranav, @.***> wrote:

I agree with you but I think there is no harm in having that package because right now its working fine in production, without out it might or might not.. Closing issue for now, reopen if required.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ALPHAVIO/BlogSite/issues/319#issuecomment-798007888, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKG5GE56ESURVDTNZWHYHDTTDMU2FANCNFSM4ZDQNGBQ .

[Pranav016]

Because now it is inbuilt in express so no need to Install additional dependency and in vs code also it gives warning if you use bodyparser

Yes, we can remove it somewhere down the line but right now I don't want to break any code in production due to compatibility.