Using JSHint with Express.js / 'delete' (a reserved word)

Question

I'm using Express.js ontop of Node.js to create RESTful API, and using grunt to watch my files and automatically lint my JavaScript.

Every time I use the delete function, it gets flagged by JSHint:

[L218:C9] Expected an identifier and instead saw 'delete' (a reserved word).
app.delete('/api/users/:userid', function deleteUser(req, res, next) {

I understand that 'delete' is a reserved word, but it's chosen by Express.js! Is there a better way to go about linting my Express.js app? Any way to turn off this check??

Doing a quick search I believe you can use `es5` option for that. — Alfred, Jul 11 '12 at 18:10

score 28 · Accepted Answer · answered Jul 10 '12 at 19:28

28

In Express.js, use del instead of delete.

app.del('/api/users/:userid', function deleteUser(req, res, next)

answered Jul 10 '12 at 19:28

Bill

25,119
8
94
125

1

DO NOT USE del anymore! express deprecated app.del: Use app.delete instead – joonas.fi Oct 26 '14 at 20:51

score 7 · Answer 2 · edited May 23 '17 at 12:30

Another way to solve this would have been to use bracket notation instead of dot notation.

app['delete']('/api/users/:userid', function deleteUser(req, res, next) {
  /* function body */
});

This sort of work around was necessary in the past when working with IndexedDB which defines both .delete and .continue methods.

These days this sort of workaround should not be necessary. Ever since ES5 JavaScript has allowed property names to use reserved words. For a long time jsHint defaulted to assuming your code was ES3, but starting with version 2.0.0 it defaults to assuming it is ES5 and will not complain about reserved words being used as property names.

Juan Pablo Buritica · Answer 3 · 2013-06-16T19:30:26.393

3

In JSHint 1.1.x you can set the es5 option for jshint, and it will allow you to use reserved words as properties per the ES5 specification.

As of JSHint 2.0 es5 option is the default and you should be allowed to use reserved words as properties.

For more info you can head over to http://www.jshint.com/docs/#options

edited Jun 16 '13 at 19:30

answered Mar 04 '13 at 06:53

Juan Pablo Buritica

507
5
8

2

This has changed; [as of version 2.0.0](http://www.jshint.com/blog/2013-05-07/2-0-0/), JSHint got rid of the `es5` option and now assumes code is ES5 unless told otherwise via the new `es3` and `esnext` options. – Useless Code Jun 03 '13 at 20:38

Using JSHint with Express.js / 'delete' (a reserved word)

3 Answers3