You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing binary-build tools for Nodejs projects like nexe and pkg seems to have a falling activity level, and deploying binaries on macos with these tools is currently semi-broken, as resulting mach-o binaries cannot pass codesign's "strict validation" check, meaning that users have to be prompted with serious warnings and bumps, before running the executer.
I wonder if the node community might have some best-practices, knowhow or recommendations for distributing signed executers, with sign-able distributions on windows and macos in particular.
Obviously node itself is a signed binary, but reverse-engineering nodes release flow to achieve a signed binary seems daunting!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Existing binary-build tools for Nodejs projects like nexe and pkg seems to have a falling activity level, and deploying binaries on macos with these tools is currently semi-broken, as resulting mach-o binaries cannot pass codesign's "strict validation" check, meaning that users have to be prompted with serious warnings and bumps, before running the executer.
I wonder if the node community might have some best-practices, knowhow or recommendations for distributing signed executers, with sign-able distributions on windows and macos in particular.
Obviously node itself is a signed binary, but reverse-engineering nodes release flow to achieve a signed binary seems daunting!
Beta Was this translation helpful? Give feedback.
All reactions