isObject is too strict of a check for fameworks that provide access to turf eg nodered. causes many modules to reject a legitimate options object
See original GitHub issuePlease provide the following when reporting an issue:
- GeoJSON data as a gist file or geojson.io (filename extension must be
.geojson
). - Snippet of source code or for complex examples use jsfiddle.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Process object memoryUsage() - General - Node-RED Forum
I'd like to access the process object inside the function code, such as to know the memory usage of the runtime: msg.payload =...
Read more >[uibuilder new release] v5.1.1 - Some nice new features and ...
The new client library introduces the concept of configuration-driven UI's. Create a UI partially or fully from JSON data either from files, web ......
Read more >Where to define class to use in multiple nodes
These are passing json objects. To create these objects I use multiple classes. This works fine as long as the class definition is...
Read more >Problem with node-red-contrib-actionflows since upgrade to ...
Since upgrade to 2.2.0, the "action in"-process isn't triggered anymore. Log-Entry RED.settings.functionGlobalContext.get is not a function ...
Read more >Creation of external objects in function node fails (solved)
I have a problem to understand or to use external modules with new features in the function node. I tried it first the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is a major issue, yes.
node v12.16.1, turf 5.1.6:
Both of those, absolutely should resolve to true, but do not… as a result, it’s impossible to use the options param on basically any turf method.
Seems like instead of
input.constructor === Object
the check really ought to betypeof input === 'object'
@spydmobile would you please provide some examples of the actual issue? That will help us to better understanding the extent of the problem.