Open troykelly opened 1 year ago
@troykelly this smells like a libstd issue, any chance you can try upgrading that? I am not familiar with AppWrite, but I suspect it runs your application in some sort of container env.
I cant tell from the issue you linked, but what version of node are you running?
It's Node-16. I might have to raise this with the AppWrite team instead?
@troykelly do you know how AppWrite runs your code? If we can create a reproducible env, I'd be happy to investigate this
AppWrite isn't super difficult to set up, it's just time/resourcing consuming (it's easiest on a clean VM, running their online installer) If you have an AppWrite environment, just trying to publish a function that has the library in the package.json will cause the failure.
@troykelly any chance you could send us the output of running npm install --verbose --foreground-scripts @sentry/profiling-node inside appwrite?
@troykelly seems like appwrite is in private beta so we cant actually deploy functions without access. Let me know if you are able to provide us with the logs of npm install --verbose --foreground-scripts
@JonasBa AppWrite cloud is a private beta. I'm running AppWrite locally - I can't see a way to capture the npm install during build.
Is there an existing issue for this?
How do you use Sentry?
Self-hosted/on-premise
SDK Version
0.3.0
Link to Sentry event
No response
What environment is your node script running in?
Running inside AppWrite
How is your code deployed and bundled?
Daployed using AppWrite's deploy
Steps to Reproduce
@sentry/profiling-node
topackage.json
Expected Result
Deployment completes, code runs, profiling happiness ensues
Actual Result
Unable to deploy: