Skip to content

Update package.json#32

Open
darrendignam wants to merge 6 commits intoopenpreserve:masterfrom
darrendignam:master
Open

Update package.json#32
darrendignam wants to merge 6 commits intoopenpreserve:masterfrom
darrendignam:master

Conversation

@darrendignam
Copy link

When trying to compile the app on Node v17 I was getting errors error:0308010C:digital envelope routines::unsupported reading online showed this was related to openssl. The hacks and workarounds seem to disable security. But an easier option was to use Node v16 - so I have added a constraint to the node engine in the package.json"
[master e732cfa] When trying to compile the app on Node v17 I was getting errors error:0308010C:digital envelope routines::unsupported reading online showed this was related to openssl. The hacks and workarounds seem to disable security. But an easier option was to use Node v16 - so I have added a constraint to the node engine in the package.json

I also noticed that veraPDF version numbers didn't match, so made them match the current version that gets downloaded bu the download script

Darren Dignam and others added 6 commits November 2, 2021 12:35
…wnloaded did not match all the script version filenames.
…:0308010C:digital envelope routines::unsupported reading online showed this was related to openssl. The hacks and workarounds seem to disable security. But an easier option was to use Node v16 - so I have added a constraint to the node engine in the package.json
When trying to compile the app on Node v17 I was getting errors error:0308010C:digital envelope routines::unsupported reading online showed this was related to openssl. The hacks and workarounds seem to disable security. But an easier option was to use Node v16 - so I have added a constraint to the node engine in the package.json"
[master e732cfa] When trying to compile the app on Node v17 I was getting errors error:0308010C:digital envelope routines::unsupported reading online showed this was related to openssl. The hacks and workarounds seem to disable security. But an easier option was to use Node v16 - so I have added a constraint to the node engine in the package.json

I also noticed that veraPDF version numbers didn't match, so made them match the current version that gets downloaded bu the download script
Added v17 back in
Starting to build out a CI workflow for this project
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments