Closed shashank1010 closed 1 month ago
Ahh we've introduced a regression. I will fix this today hopefully.
The issue response time there was off the charts! Really appreciate it!! Kudos!
Thanks.
doesn't seem to be fixed?
doesn't seem to be fixed?
Your IDE is configured for browser environment, and not Node. A Webpack plugin will provide a static value to the property notation process.node.version
in the browser.
IDE squiggles are not bugs
The issue response time there was off the charts! Really appreciate it!! Kudos!
Thanks.
Oh you're welcome! Just had a free moment and that error is a familiar problem hehe
Your IDE is configured for browser environment, and not Node. A Webpack plugin will provide a static value to the property notation
process.node.version
in the browser.IDE squiggles are not bugs
This is not an IDE, this is chrome dev tools, it's a browser. I'll investigate more, might be a bun bug
edit: not a bun bug, same problem with yarn
https://github.com/deepgram/deepgram-js-sdk/assets/34604972/2b13a934-762a-4d0b-8856-a9363c61cf86
could it be a cache issue? something else?
Hi! I'm facing the same issue right now. I have a SvelteKit app. When I import the SDK:
<script lang="ts">
import { createClient } from '@deepgram/sdk';
</script>
I get the following error:
@lukeocodes the problem persists in version 3.3.1 with vite and other environments. it did not exist in 3.2.0 yet... could we please reopen this issue?
Hi, I'm also getting this same issue, also with vite & sveltekit.
There is a PR up by a community member to resolve this, it has comments that need addressing
@lukeocodes Yes, thanks for pointing this out I commented there. To me the problem lies deeper honestly, first you introduced the new requirement to have a process.env
variable during build with a patch version release (yes, that broke our product). Secondly, it is not documented anywhere, that this is even necessary, so everyone using your sdk for the first time (unless they happen to use webpack and copy your example) will end up with this issue. Lastly, as written in the other comment, I do not understand your motivation in the first place, what's the benefit of tracing a build time nodejs version which does not have any meaning for the actual runtime of your sdk? Please make the requirement on the process.env
optional again or at least document it properly and release a new version reflecting this breaking change, thanks!
@lukeocodes HI, i just tried this on browser, this issue is still present on sdk v3.3.3, also tried sdk v3.3.1 same error
created a ticket on discord as well
@lukeocodes HI, i just tried this on browser, this issue is still present on sdk v3.3.3, also tried sdk v3.3.1 same error
created a ticket on discord as well
In vite built apps?
@lukeocodes HI, i just tried this on browser, this issue is still present on sdk v3.3.3, also tried sdk v3.3.1 same error
created a ticket on discord as well
In vite built apps?
Create react app
@lukeocodes HI, i just tried this on browser, this issue is still present on sdk v3.3.3, also tried sdk v3.3.1 same error created a ticket on discord as well
In vite built apps?
Create react app
hmmm understood. we need a better solution, we see that
What is the current behavior?
Installing v3.3.0 results in the error
Uncaught ReferenceError: process is not defined
What's happening that seems wrong?
It seems that the dist bundle is not correct. dist bundles should have references to
process
objectSteps to reproduce
Expected behavior
Please tell us about your environment
Other information
Reverting to v3.2.0 resolves the issue.
Anything else we should know? (e.g. detailed explanation, stack-traces, related issues, suggestions how to fix, links for us to have context, eg. stack overflow, codepen, etc)