How to avoid circular reference in OOP Javascript?

From what you've described, you don't need a circular reference at all, so the best thing you can possibly do is get rid of it completely.

in Column class I have a build function which return a string by combining table and column like "tableA.colB". That why column need to know what table it belong to.These entities are used for building SQL statement.

This is a sign that your build function does not belong on the Column class. Think about it: Why is a single Column in your database the object responsible for building part of an SQL statement? You probably want to do the SQL building in an entirely separate class that's actually designed for that purpose.

class SQLBuilder {
    build: function(table, column) {
        return ... + table.name + "." + column.name + ...;
    }
}

If for some reason this isn't an option, there are tricks you can resort to like storing the name of the parent table instead of a direct reference (which has most of the downsides of a real circular reference other than "breaking" toJSON), or implementing custom serialization logic (which is really tedious and error-prone code to maintain), but you shouldn't do things like that unless you have a very good reason to.

The easiest way, as mentioned in comments, is to remove the Parent reference from Column as mentioned in the comments. You can almost certainly recode to provide both the table and column as a pair (instead of just the column) wherever needed.

The next easiest way is to change the content of the Parent in Columns from an object reference to an id of some sort, whether an integer whose value corresponds to an index into an array of tables, or a string that holds the unique id or name of the table. This means your usages of column.Parent, if they need access to the whole table, will need to be wrapped in a function that understands how to translate the index or string into the parent.

Note that if your table names are unique and that is all you need from column.Parent, then perhaps converting these fields from a (circular) reference to another object into a string that identifies the name of the table will work best for you.

The next method is to provide a custom toJSON() for Column types so that they alter the Parent field for serialization, alter it from a reference to an index or string as per the above; this will then only happen during JSON.stringify() instead of during routine in-memory use of that field. Of course, to do this you'll also have to create or simulate a reviver operation during/after JSON.parse() that understands the references and converts them back to the objects.