Open lwlsn opened 5 months ago
Logged an issue in pulsar but it looks like it might be package specific?
What is the code you are evaluating?
On Sun, Apr 14, 2024, 11:44 Lizzie @.***> wrote:
Logged an issue in pulsar but it looks like it might be package specific?
pulsar-edit/pulsar#969 https://github.com/pulsar-edit/pulsar/issues/969
— Reply to this email directly, view it on GitHub https://github.com/hydra-synth/atom-hydra/issues/66#issuecomment-2054131761, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABFOVSKNEG5VJTSKBJ2HADTY5K573AVCNFSM6AAAAABGGILQ4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUGEZTCNZWGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Ah apologies- The package toggles on/off; but then when you evaluate any code in the editor Pulsar throws this error.
I've made sure to install via the readme instructions, and also tried a npm install and still get the same error :/
so even just osc().out()
would throw this
I've tried package installs for hydra in Pulsar using both ppm and npm following the latest instructions on the Readme.
This error appears when evaluating code in the editor:
This is the eval-code is keymapped and producing the error
Any suggestions as to what's going on here?
I'm running on a Mac M3