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
As a module author or deno deploy user I'd love a way to know if my script will run on deno deploy without having to actually deploy my code. For instance I just learned about std/node being merged into deno, I believe you're supposed to use the node: path modifier. I just changed my imports and found it didn't work on deploy. I'd love a way to add a flag in github actions --deploy-compatible and get pass / fail and know why before I run it in deploy. It's confusing to have things work locally and not work on deploy, better scriptable transparency would be great!
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
-
As a module author or deno deploy user I'd love a way to know if my script will run on deno deploy without having to actually deploy my code. For instance I just learned about
std/node
being merged into deno, I believe you're supposed to use thenode:
path modifier. I just changed my imports and found it didn't work on deploy. I'd love a way to add a flag in github actions--deploy-compatible
and get pass / fail and know why before I run it in deploy. It's confusing to have things work locally and not work on deploy, better scriptable transparency would be great!Beta Was this translation helpful? Give feedback.
All reactions