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
Hi @wobsoriano ! So I recently made a PR for toast.loading. I'll just preface that this bug is not related to that. I think there's something wrong with how the files are being bundled into npm.
The bug
The Loading Icon doesn't appear when solid-sonner is installed from npm. It's actually also happening on the https://solid-sonner.vercel.app/ demo.
When installed from local, it seems to work just fine. (both are the same versions by the way).
Versions I've tried with
So as mentioned, the toast.loading() PR is not the cause because the bug seems to be the same for the previous versions. I do think it's fair that it wasn't caught though. It only works in local, but breaks in npm. Kind of weird.
0.2.7 - version where I added the toast.loading()
0.2.6 - previous version before my PR
Investigation/Reproduction Steps
When I install solid-sonner locally to my project, there's no issues.
When I install solid-sonner via npm, this issue comes up.
bun install solid-sonner
I installed both and did some diffing and there were some very particular lines that might be the culprits.
# installed the local first.
bun install /Users/carlo/Desktop/Projects/solid-sonner
# installed the npm. This won't work in runtime, we just want to diff
bun install solid-sonner-npm@npm:solid-sonner
# Diff them in VSCode
code --diff node_modules/solid-sonner/dist/dev.js node_modules/solid-sonner-npm/dist/dev.js
In line 31, this was the diff (first paragraph is the local 🍎, second is the npm 🍏)
You might notice that for the npm one, there's class=sonner-loading-wrapper>, etc. Basically it removes the quotes. I don't think that's valid HTML, so as a result the template probably doesn't get parsed on the browser.
This bundling is kind of not my expertise though. Do you have an idea on why this might happen?
EDIT: So it's not the quotes. I might have to look into this more a bit.
The text was updated successfully, but these errors were encountered:
After looking into this, it actually wasn't the diff I mentioned. I think it was just the <Dynamic /> component in Solid. I couldn't figure out a better solution but so far, just copying the syntax from the original Sonner (react) works fine.
Hi @wobsoriano ! So I recently made a PR for
toast.loading
. I'll just preface that this bug is not related to that. I think there's something wrong with how the files are being bundled into npm.The bug
The Loading Icon doesn't appear when
solid-sonner
is installed from npm. It's actually also happening on the https://solid-sonner.vercel.app/ demo.When installed from local, it seems to work just fine. (both are the same versions by the way).
Versions I've tried with
So as mentioned, the
toast.loading()
PR is not the cause because the bug seems to be the same for the previous versions. I do think it's fair that it wasn't caught though. It only works in local, but breaks in npm. Kind of weird.0.2.7
- version where I added thetoast.loading()
0.2.6
- previous version before my PRInvestigation/Reproduction Steps
solid-sonner
locally to my project, there's no issues.solid-sonner
via npm, this issue comes up.In line 31, this was the diff (first paragraph is the local 🍎, second is the npm 🍏)
You might notice that for the npm one, there's
class=sonner-loading-wrapper>
, etc. Basically it removes the quotes. I don't think that's valid HTML, so as a result the template probably doesn't get parsed on the browser.This bundling is kind of not my expertise though. Do you have an idea on why this might happen?
EDIT: So it's not the quotes. I might have to look into this more a bit.
The text was updated successfully, but these errors were encountered: