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
I just recently learned about svelte and am currently learning it. I saw a svelte summit where you held a talk and got to know your projects, that MacOS Web thing is really cool btw :)
I wanted to try neodrag, so I added it to the Svelte Realworld project that I'm using to play around with.
It worked like a charm... until I used a environment variable in my code. Neodrag seems not to generate the whole code (including classes like neodrag on the element itself) when accessing process.env.
I created a stackblitz for you, so you can easily see what I mean. What's interessting, it's not only that when I use an environment variable "inside" an element that should be draggable, but also when I just access the process.env property within a script tag.
I checked ur demo, biggest issue is that sveltekit doesn't support process. Because process isn't there, whole code errors and stops execution, hence the imports, which are below the console.log(process..., are not executed at all.
So avoiding use of process will fix it. Instead use import.meta.env
I just recently learned about svelte and am currently learning it. I saw a svelte summit where you held a talk and got to know your projects, that MacOS Web thing is really cool btw :)
I wanted to try neodrag, so I added it to the Svelte Realworld project that I'm using to play around with.
It worked like a charm... until I used a environment variable in my code. Neodrag seems not to generate the whole code (including classes like
neodrag
on the element itself) when accessingprocess.env
.I created a stackblitz for you, so you can easily see what I mean. What's interessting, it's not only that when I use an environment variable "inside" an element that should be draggable, but also when I just access the process.env property within a script tag.
Stackblitz Container.
Maybe you can help me to figure out what the issue is.
The text was updated successfully, but these errors were encountered: