Gets the job done when JSON.stringify can't
Last updated a year ago by pi0 .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @nuxt/devalue 
SYNC missed versions from official npm registry.


npm version npm downloads Circle CI package phobia bundle phobia

Forked from devalue to log errors on non-serializable properties rather than throwing Error.

Like JSON.stringify, but handles

  • cyclical references (obj.self = obj)
  • repeated references ([value, value])
  • undefined, Infinity, NaN, -0
  • regular expressions
  • dates
  • Map and Set
  • .toJSON() method for non-POJOs

Try it out on runkit.com.



  • Human-readable output
  • Stringifying functions or arbritary non-POJOs


import devalue from '@nuxt/devalue';

let obj = { a: 1, b: 2 };
obj.c = 3;

devalue(obj); // '{a:1,b:2,c:3}'

obj.self = obj;
devalue(obj); // '(function(a){a.a=1;a.b=2;a.c=3;a.self=a;return a}({}))'

If devalue encounters a function or a non-POJO, it will throw an error.

XSS mitigation

Say you're server-rendering a page and want to serialize some state, which could include user input. JSON.stringify doesn't protect against XSS attacks:

const state = {
  userinput: `</script><script src='https://evil.com/mwahaha.js'>`

const template = `
  var preloaded = ${JSON.stringify(state)};

Which would result in this:

  var preloaded = {"userinput":"</script><script src='https://evil.com/mwahaha.js'>"};

Using devalue, we're protected against that attack:

const template = `
  var preloaded = ${devalue(state)};
  var preloaded = {userinput:"\\u003C\\u002Fscript\\u003E\\u003Cscript src=\'https:\\u002F\\u002Fevil.com\\u002Fmwahaha.js\'\\u003E"};

This, along with the fact that devalue bails on functions and non-POJOs, stops attackers from executing arbitrary code. Strings generated by devalue can be safely deserialized with eval or new Function:

const value = (0,eval)('(' + str + ')');

Other security considerations

While devalue prevents the XSS vulnerability shown above, meaning you can use it to send data from server to client, you should not send user data from client to server using the same method. Since it has to be evaluated, an attacker that successfully submitted data that bypassed devalue would have access to your system.

When using eval, ensure that you call it indirectly so that the evaluated code doesn't have access to the surrounding scope:

  const sensitiveData = 'Setec Astronomy';
  eval('sendToEvilServer(sensitiveData)'); // pwned :(
  (0,eval)('sendToEvilServer(sensitiveData)'); // nice try, evildoer!

Using new Function(code) is akin to using indirect eval.

See also



Current Tags

  • 1.2.4                                ...           latest (a year ago)

5 Versions

  • 1.2.4                                ...           a year ago
  • 1.2.3                                ...           2 years ago
  • 1.2.2                                ...           2 years ago
  • 1.2.1                                ...           2 years ago
  • 1.2.0                                ...           2 years ago
Today 350
This Week 4,674
This Month 19,448
Last Day 1,290
Last Week 5,635
Last Month 26,142
Dependencies (1)
Dev Dependencies (11)

Copyright 2014 - 2017 © taobao.org |