I'm using jshint to validate my JavaScript files.

On the server-side I'm using node.js with Mongoose. In Mongoose I'm encouraged to write schemata in a fashion like:

var UserSchema = new mongoose.Schema({
    firstname : { type: String, default: '' }
});

When running linting, I get error:

Expected an identifier and instead saw 'default' (a reserved word).

Is there a way to suppress this error? I really would prefer that behaviour instead of writing:

var UserSchema = new mongoose.Schema({
    firstname : { type: String, "default": '' }
});

I'm using jshint to validate my JavaScript files.

On the server-side I'm using node.js with Mongoose. In Mongoose I'm encouraged to write schemata in a fashion like:

var UserSchema = new mongoose.Schema({
    firstname : { type: String, default: '' }
});

When running linting, I get error:

Expected an identifier and instead saw 'default' (a reserved word).

Is there a way to suppress this error? I really would prefer that behaviour instead of writing:

var UserSchema = new mongoose.Schema({
    firstname : { type: String, "default": '' }
});

• javascript
• node.js
• mongoose
• jslint
• jshint

• 1 Technically speaking, that is invalid JS, although most environments seem to allow it. I'm not sure if there is a configuration option in JSHint though. – Dominic Barnes Commented Jun 7, 2012 at 18:48
• I really get the point in that. Why does Mongoose suggest us to write invalid JS? :/ – jsalonen Commented Jun 7, 2012 at 20:49
• 1 Just put it in quotes and move on. It bugged me at first too, but now I feel like a dope for even spending time thinking about it. – JohnnyHK Commented Jun 7, 2012 at 21:00
• @JohnnyHK I share that feeling right now. Moving on. – jsalonen Commented Jun 8, 2012 at 18:02

2 Answers 2

default is indeed a reserved word in JavaScript (https://developer.mozilla/en/JavaScript/Reference/Reserved_Words). While technically you can use default in an object property name without any problems, you could end up having problems with that notation if your interpreter is strict (like lint is).

Simplest way to go forward: fix the problem by adding quotes. Lint won't whine you any longer. The code is two characters longer, but so what - linting passes and you are guaranteed to not have problems due to use of a reserved keyword.

You can also use the "es5" option to disable this from occurring.

See: http://jslinterrors./expected-an-identifier-and-instead-saw-a-a-reserved-word/