License issue after upgrading Node version
License issue after upgrading Node version
Hi, I have a React project that uses the "datatables.net-editor": "^1.6.5" library. I've been working on migrating from React v16 to v18 and as a result have upgraded the node and npm versions that we use with the project.
After doing this I noticed the editor license no longer seems to work. I'm seeing the "the licensed or trial files have not been installed in place of the holding files." info logs in console. However, I'm running the install.js script in the editor library with node node_modules/datatables.net-editor/install.js ./Editor-NodeJS-1.9.4.zip
and restarting my project with no success.
Is there a known issue with node v20 and the editor package? Is there a workaround so I can get this to work?
I'll list my package.json contents below and node/npm versions
Node: v20.19.1
Npm: 11.5.1
"dependencies": {
"@aws-amplify/ui-react": "^6.11.2",
"@babel/preset-env": "^7.12.1",
"@babel/preset-flow": "^7.12.1",
"@babel/preset-react": "^7.12.1",
"@hello-pangea/dnd": "^18.0.1",
"@testing-library/jest-dom": "^4.2.4",
"@testing-library/react": "^13.4.0",
"@testing-library/user-event": "^14.6.1",
"@tippy.js/react": "^3.1.1",
"aws-amplify": "^6.15.4",
"axios": "^1.11.0",
"bignumber.js": "^9.1.2",
"datatables.net": "github:DataTables/Dist-DataTables#0c4d61ff1117809030a5a3ca5e3509024dba7f3a",
"datatables.net-buttons": "^1.6.2",
"datatables.net-buttons-dt": "^1.6.2",
"datatables.net-buttons-se": "^1.6.2",
"datatables.net-colreorder": "^1.7.0",
"datatables.net-colreorder-dt": "^1.7.0",
"datatables.net-colreorder-se": "^1.7.0",
"datatables.net-dt": "^1.13.6",
"datatables.net-editor": "^1.6.5",
"datatables.net-editor-dt": "^1.6.3",
"datatables.net-editor-se": "^1.6.3",
"datatables.net-se": "^1.13.6",
"datatables.net-select": "^1.3.1",
"datatables.net-select-dt": "^1.3.1",
"datatables.net-select-se": "^1.3.1",
"formik": "^2.2.9",
"history": "^5.3.0",
"identity-obj-proxy": "^3.0.0",
"jquery": "^3.7.1",
"jsbarcode": "^3.11.0",
"jspdf": "^2.5.1",
"jspdf-autotable": "^3.5.23",
"papaparse": "^5.5.3",
"qs": "^6.9.4",
"react": "^18.3.1",
"react-barcode": "^1.4.0",
"react-datepicker": "^4.7.0",
"react-dom": "^18.3.1",
"react-promise-tracker": "^2.1.0",
"react-redux": "^9.2.0",
"react-router-dom": "^7.7.1",
"react-scripts": "^5.0.1",
"react-settings-pane": "^0.1.5",
"react-test-renderer": "^18.3.1",
"react-to-print": "^2.10.0",
"react-tooltip": "^4.2.21",
"redux": "^5.0.1",
"redux-thunk": "^3.1.0",
"semantic-ui-css": "^2.4.1",
"semantic-ui-react": "^2.1.5",
"tippy.js": "^6.3.1",
"uniqid": "^5.2.0",
"xlsx": "^0.18.5",
"yup": "^0.32.11"
},
This question has an accepted answers - jump to answer
Answers
I'm not aware of any such issue I'm afraid. Can you show me the output of the
install.js
command? Also what's the output ofand
Thank you,
Allan
Hey Allan, it started working after using a
post-install
script in the package.json rather than manually executing the install script. No idea why, perhaps my browser was caching. I'll mark this as completed