node-logger | Centralized logger for 17.Media Node.JS projects | Runtime Evironment library

There's no such concept as

the length of the allocated memory and length of the "logical" memory differ from each other

in JavaScript, at least not as far as the user is concerned.

You might be looking for container.innerText instead. I think the whitespace you're seeing in textContent is a result of otherwise folded DOM whitespace being there, ref.

For other node types, textContent returns the concatenation of the textContent of every child node, excluding comments and processing instructions.
– MDN

seems you're missing something ... here's an example

To get whole URL address use:

The issue is from you apply the rule for your import without options like this:

Babel had stopped supporting Stage Presets in the configuration. Read this article.

By running this command :

ExtendScript is ES3, so I'm not sure which kind of magic those monkey patches are pulling in order to make this archaic format run like Node. It would seem to me though that something about that is failing in your case. As the node stuff is in a whole different kind of javascript, it's likely that this approach is not possible.

You probably can have a separate node application that can interact with your jsx scripts. Mainly, it can manipulate your InDesign via running jsx scripts on it that perhaps carry arguments and return results to it.

It would kind-of hinge on being able to replicate AppleScript's 'do javascript' command which runs is available within a 'tell an adobe application' block and can execute dynamically-made javascripts with arguments as well as return the results synchronously.

I'm not sure how to make sure all the users have the right items installed on their systems - for running the Node. Maybe they all have to make some kind of installer. For example, when writing a simple jsx script all you have to do is provide the script to the users, but with this hypothetical setup it's not clear to me at this moment.

Alternatively, the next step up is a CEP extension which can use Node and the browser in it and also can run jsx scripts and get the results, etc. The main obstacle with this is the amount of work needed to make the entire project work, it is an overwhelming amount of information at first and carries perhaps a lot more overhead than making a simple custom node application which uses jsx routines.

If you find a way to provide easy-to-install cross-platform node-jsx application to users, that may be a quick method for delivering powerful scripted apps to the users in those cases where all the flare of a built-in browser UI is too much effort for the intended usage. For example, if you wish to do some application control in Node that jsx can't do, and are able to get by with the ExtendScript ScriptUI or other means for the UI then it would work out well.

Put the code