Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issues running jazzer in node v14 #641

Closed
karfau opened this issue Oct 9, 2023 · 1 comment · Fixed by #672
Closed

Issues running jazzer in node v14 #641

karfau opened this issue Oct 9, 2023 · 1 comment · Fixed by #672

Comments

@karfau
Copy link

karfau commented Oct 9, 2023

The engine in package.json claims that nodejs version >=14 is supported/required. But when using the most recent version of Node 14 (as part of a test) I get the following output:

     TypeError: Object.hasOwn is not a function
       at node_modules/@jazzer.js/core/options.ts:207:15
           at Array.forEach (<anonymous>)
       at mergeOptions (node_modules/@jazzer.js/core/options.ts:205:31)
       at node_modules/@jazzer.js/core/options.ts:179:11
           at Array.reduce (<anonymous>)
       at buildOptions (node_modules/@jazzer.js/core/options.ts:176:4)
       at loadConfig (node_modules/@jazzer.js/jest-runner/config.ts:52:21)

https://github.com/xmldom/xmldom/actions/runs/6452742416/job/17515178816#step:7:64

The GitHub action workflow that is used for testing in the jazzer.js repository is using node v16.

Should the value in the engines field be bumped or are you still trying to support node v14?
@oetr
Copy link
Contributor

oetr commented Oct 9, 2023

Thanks for reporting this!
I think we do want to support node v14, so we'll take a look.

@bertschneider bertschneider mentioned this issue Oct 24, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix node.js v14 support CodeIntelligenceTesting/jazzer.js
2 participants
@karfau @oetr