In effort to keep a consistent codestyle and catch bugs, switch using standard for eslinting.

On https://github.com/marcello3d/node-tosource/blob/master/tosource.js#L23, instead of return just {$circularReference:1} it would be good to return the actual index of the circular reference, so they can be identified as different ones.

When using the usual ESM stuff, I still resolve to index.js instead of index.esm.js.

import { createRequire } from "node:module";
const require = createRequire(import.meta.url);

console.table({
  "is-what": {
    esm: import.meta.resolve("is-what"),
    cjs: require.resolve("is-what"),
  },
  tosource: {
    esm: import.meta.resolve("tosource"),
    cjs: require.resolve("tosource"),
  },
});

(Using is-what as an example of it done OK-ly)

I think this could be solved by using modern exports: {} conditions instead of main and module? But even this is not recommended so as to avoid the dual package hazard https://nodejs.org/api/packages.html#packages_dual_package_hazard where you can get two copies of the package code in your webpack/vite/rollup/parcel/whatever bundle.js file.

The idealized solution is to either a) only export an ESM version or b) export an ESM wrapper that just export {} from "./module.cjs" so that there's only one canonical source of code or c) only export a CJS version.

Funnily enough, in the package's current state it doesn't suffer from the dual package hazard since it currently only exports CommonJS 🤣

Hi,

it gives //slash/killed/me/ which isn't evaluable.
just got bitten by this, using an old nodejs 0.10 + v8 3.14 version from debian.
Maybe 0.12 or io.js don't have that problem (i.e. properly escape regexp toString).

It is not obvious how to use npm to install this... since the github project name is different than the npm name...

Just might save your more ignorant users (like me) some forehead wrinkling...

I don't have time to file a PR right now but can try and do so later - just thought I'd flag this in the meantime:

foo = [];
obj = { foo: foo, bar: foo };

toSource( obj );
// -> "{ foo:[  ], bar:{$circularReference:1} }"

Expected would be { foo:[], bar:[] } since foo doesn't contain bar.

Array with last element as a hole will generate wrong output.

eval(tosource(Array(3))).length // should be 3, but get 2 

In my case, the output contains function () { [native code] } so that it's invalid to be read by the browser.

Hello,

We want to use the tosource package, but in NPM, the license is showing as "none" on the right hand side(under weekly downloads).

Because of this our automated package checker is unable to download and rejecting the package I guess. Could you please help update the license on NPM?

Thanks a lot!!! @marcello3d

Package on NPM ([email protected]) is missing the dist folder, so does not function.

The NPM package also includes src folder, which is unnecessary. It could be excluded from the NPM release with a files field in package.json, or an .npmignore file.

Is it possible?

I want to catch and rewrite it as 'console.trace(' + toSource(e) + ')'

Standard on Javascript for source code are the single quotes (') instead of the double quote (") to distingish from HTML attributes, and in fact Node.js use single quotes when showing an object on the console. Double quoted strings has the advantage that they can be easily generated with JSON.stringify(), but it should be better to use single quotes and the encode() function or another similar one.

Hi,

I want to inject the following options to a google chart within an html page:
slices: { 0: { color: 'yellow' }, 1: { color: 'transparent' } }
(see gchart help)

So I first build a slice object:

slices= {};
slices[0]={ color: 'yellow' }; 
slices[1]={ color: 'transparent' };

Then I call toSource(slices) and get the following result:

{ "0":{ color:"yellow" }, "1":{ color:"transparent" } }

Sadly, google charts doesnt like the String keys instead of integers. I'll find a workaround for that, but I think toSource is misbehaviying. I know it is not really part of a standard, but I can't see why the integers should get casted into Strings. Firefox's toSource() is keeping integers as integers, I think it would make more sense to do so.

toSource(`test${process.env.HOME}`)

i'm not sure it's possible.

Luckily

toSource(function() {`test${process.env.HOME}`})

already works all right.

Split the code in several functions and set it to the prototype object of the diferent classes to polyfill the functionality that Firefox offer. The current tosource() could still be exported to be backwards compatible, only that internally would call the per-object functions.

"typings": "./dist/index.d.ts",

./dist/index.d.ts does not exists.
It seems like it should be ./dist/tosource.d.ts.

Hi, first off: thanks for the nice piece of code!

My issue:

m = new Map
m.set("key1", 42)
m.set("key2", "some value")
toSource(m)

Returns "{}"
It would be nice if it returned
{"key1": 42, "key2": "some value"}

Any chance you would have time to implement something like this?

tosource(-0) should return '-0' instead of '0'

Object.is(eval(tosource(-0)), -0); // should be true