Created by Shared Doc User, last modified by N Padmavathi on Sep 25, 2020
2.3.5
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 27115 | Missing link between NODE-JS operation to JS function |
2.3.4
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 26135 | Extension com.castsoftware.nodejs has encountered an issue: IndexError: string index out of range |
2.3.3
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 26040 | Extension com.castsoftware.nodejs has encountered an issue: RuntimeError: invalid type name: 'CAST_NodeJS_AWS_Lambda_ANY' |
2.3.2
Note
Node.js - 2.3.2 is now in LTS (Long Term Support).
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 24720 | Broken link between HTML5 Javascript function and NodeJS MongoDB Collection. |
| 23004 | Extension com.castsoftware.nodejs has encountered an issue |
| 23785 | HTML analysis getting crashed while analyzing .js file |
Other Updates
| Details |
|---|
| com.castsoftware.nodejs has encountered an issue: found duplicate key "<<" |
| com.castsoftware.nodejs has encountered an issue: AttributeError: 'NoneType' object has no attribute 'values' |
| com.castsoftware.nodejs has encountered an issue: ScannerError: while scanning for the next token found character '@' that cannot start any token |
| com.castsoftware.nodejs has encountered an issue |
| com.castsoftware.nodejs has encountered an issue: ReaderError: unacceptable character #x0080: special characters are not allowed |
| com.castsoftware.nodejs has encountered an issue: ScannerError: while scanning for the next token |
| fallback to UTF-8 encoding if open_source_file does not get it right |
2.3.1-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|
| 24212 | Fatal Python error: Cannot recover from stack overflow, line 217 in get_require_declaration. |
| 24667 | Missing NodeJS Express operation |
| 23507 | Extension Node.js has encountered an issue |
| 23956 | Extension Node.js has encountered an issue ReaderError: unacceptable character #x0080:special characters are not allowed in "<unicode string>" |
Other Updates
| Details |
|---|
| StackOverflow on some app |
New Support
| Summary | Details |
|---|
| Support for Node.js v14 | Node.js - 2.3.1-funcrel supports Node.js v14. |
2.3.0-funcrel
Updated the extension to funcrel.
2.3.0-beta4
New Quality Rules
Following table lists the new quality rules added in this release.
| Internal ID | Summary |
|---|
| APLNJS-258 | Avoid using serialize-to-js 0.5.0 with Node.js |
| APLNJS-260 | Avoid using moment before 2.19.3 with Node.js |
Resolved issues
Following table lists the bug resolved in this release.
| Internal ID | Summary |
|---|
| APLNJS-255 | NodeJS analysis is failing with error "Fatal Python error: Cannot recover from stack overflow" |
2.3.0-beta3
Resolved issues
Following table lists the bug resolved in this release.
| Internal ID | Summary |
|---|
| APLNJS-252 | Extension com.castsoftware.nodejs has encountered an issue: KeyError: 'provider' |
2.3.0-beta2
Updates
| Internal ID | Summary |
|---|
| APLNJS-241 | Support of serverless config file with a different name |
New Quality Rules
Following table lists the new quality rules added in this release.
| Internal ID | Summary |
|---|
| APLNJS-247 | Avoid using Node.js synchronous FileSystem API without try/catch block |
| APLNJS-248 | Avoid using Buffer deprecated APIs |
| APLNJS-250 | Avoid using node-serialize 0.0.4 with Node.js |
Resolved issues
Following table lists the bugs resolved in this release.
| Internal ID | Summary |
|---|
| APLNJS-244 | HTML5 analysis failed with error in NodeJS - Analysis Runner stopped working. This was caused by a recursion overflow in the analyzer |
2.3.0-beta1
Updates
| Internal ID | Summary |
|---|
| APLNJS-214 | Add support for Elasticsearch |
Resolved issues
Following table lists the bugs resolved in this release.
| Internal ID | Summary |
|---|
| APLNJS-232 | [com.castsoftware.nodejs] Seneca.add() could not be analysed |
