Closed pleaseshutup closed 1 year ago
So far the only bug i've noticed is sending referrer: 'no-referrer' with fetch causes errors in node 18. Remove that and you are likely good to go.
npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@zilliqa-js/account@3.3.4', npm WARN EBADENGINE required: { node: '>=12.0.0 <17' }, npm WARN EBADENGINE current: { node: 'v18.13.0', npm: '8.19.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@zilliqa-js/blockchain@3.3.4', npm WARN EBADENGINE required: { node: '>=12.0.0 <17' }, npm WARN EBADENGINE current: { node: 'v18.13.0', npm: '8.19.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@zilliqa-js/contract@3.3.4', npm WARN EBADENGINE required: { node: '>=12.0.0 <17' }, npm WARN EBADENGINE current: { node: 'v18.13.0', npm: '8.19.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@zilliqa-js/core@3.3.4', npm WARN EBADENGINE required: { node: '>=12.0.0 <17' }, npm WARN EBADENGINE current: { node: 'v18.13.0', npm: '8.19.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@zilliqa-js/proto@3.3.4', npm WARN EBADENGINE required: { node: '>=12.0.0 <17' }, npm WARN EBADENGINE current: { node: 'v18.13.0', npm: '8.19.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@zilliqa-js/util@3.3.4', npm WARN EBADENGINE required: { node: '>=12.0.0 <17' }, npm WARN EBADENGINE current: { node: 'v18.13.0', npm: '8.19.3' } npm WARN EBADENGINE } npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@zilliqa-js/zilliqa@3.3.4', npm WARN EBADENGINE required: { node: '>=12.0.0 <17' }, npm WARN EBADENGINE current: { node: 'v18.13.0', npm: '8.19.3' } npm WARN EBADENGINE }
Hey,
Thanks for reporting this issue.
This repository is legacy and will soon be turned into a public archive. Please use https://github.com/Zilliqa/zilliqa-developer/ going forward.
So far the only bug i've noticed is sending referrer: 'no-referrer' with fetch causes errors in node 18. Remove that and you are likely good to go.