fixy icon indicating copy to clipboard operation
fixy copied to clipboard

EBADENGINE Unsupported engine

Open tobiascarlen opened this issue 1 year ago • 2 comments


Please ignore. I didn't know to use: var fixy = require('fixy'); at the start of code. I know now :)


I am probably doing something wrong, very inexperienced with javascript....

PS C:\users\toca\node> npm install fixy --save npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@azure/[email protected]', npm WARN EBADENGINE required: { node: '10 || 12 || 14 || 16 || 18' }, npm WARN EBADENGINE current: { node: 'v20.10.0', npm: '10.2.3' } npm WARN EBADENGINE }

up to date, audited 143 packages in 844ms

54 packages are looking for funding run npm fund for details

found 0 vulnerabilities PS C:\users\toca\node>

fixy appears in packages.json: "dependencies": { "fixy": "^1.3.3", "mssql": "^10.0.1", "tedious": "^16.6.0" },

but does not work. Trying to run sample code:

var fixy = fixy.parse({ map:[{ name: "Age", width: 2, start: 1, type: "int" },{ name: "Initial", width: 3, start: 3, type: "string" }], options:{ fullwidth: 5, skiplines: null, format: "csv" } }, "21ABC\n22DEF");

Results in:

C:\Users\toca\node\VDA.js:16 var fixy = fixy.parse({ ^

TypeError: Cannot read properties of undefined (reading 'parse') at Object. (C:\Users\toca\node\VDA.js:16:17) at Module._compile (node:internal/modules/cjs/loader:1376:14) at Module._extensions..js (node:internal/modules/cjs/loader:1435:10) at Module.load (node:internal/modules/cjs/loader:1207:32) at Module._load (node:internal/modules/cjs/loader:1023:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12) at node:internal/main/run_main_module:28:49

Node.js v20.10.0 PS C:\Users\toca\node>

tobiascarlen avatar Nov 30 '23 09:11 tobiascarlen

This is weird. I figured out that the warnings was caused by fixy not supporting NODE versions after 18. I installed NPM and installed and used node v18.17.0, then the install runs without warnings. But the error when running the sample still remains. I don't understand.

tobiascarlen avatar Nov 30 '23 10:11 tobiascarlen

The above problem occured running node on windows server 2016. Thinking that the issue might be windows-related, I installed fixy on ubuntu instead. Here, installation went without warnings, despite node v20.9.0. But when running the sample code, I get exactly the same error message . I am assuming there is something basic I'm missing regarding using packages under javascript, but I can not find any sample code using fixy that shows me what I am missing.

tobiascarlen avatar Nov 30 '23 10:11 tobiascarlen