Runtime Error in snowpack "TypeError: callBind is not a function" #3011
Replies: 9 comments 16 replies
-
I'm seeing this as well. If I open the source inside the browser I see this, with an error on line 41 indicating
|
Beta Was this translation helpful? Give feedback.
-
Did you find a solution? |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, I had the same results, several attempts at getting snowpack
working, but in the end, reverted back to using webpack.
…On Sun, May 16, 2021 at 9:02 PM PaulBunker ***@***.***> wrote:
Ah, that's a shame. I spent over 12 hrs trying to get snowpack working on
a large project yesterday with multiple problems, back to webpack for me
too, for now. It was wishful thinking in retrospect. Thanks for the quick
reply
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3011 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAEFKGN5VAFCWAJKSGDEIDTOCIM3ANCNFSM4Z3REYUA>
.
--
Chris Dawson
971-533-8335
Human potential, travel and entrepreneurship: http://webiphany.com/
Check out Teddy Hyde, Android editor for GitHub (especially Jekyll blogs):
bit.ly/16BL13z
|
Beta Was this translation helpful? Give feedback.
-
This happened to me recently after updating to 3.4.0. Any word on a fix? I have reverted to 3.0.10 (the previous version) for the time being. |
Beta Was this translation helpful? Give feedback.
-
Looks like this issue might be related? |
Beta Was this translation helpful? Give feedback.
-
Months later and I still am stuck an version |
Beta Was this translation helpful? Give feedback.
-
Chiming to mention that I've run into this issue trying to include the blueprintjs React framework, which includes call-bind somewhere down the dependency tree. Has anybody found a workaround for this other than downgrading to 3.0.13, or are many ubiquitous JS libraries just not usable at all with the current version of snowpack? |
Beta Was this translation helpful? Give feedback.
-
I did some digging into this and am confident that the issue crept in when snowpack upgraded The issue has to do with how @rollup/plugin-commonjs handles the resolution of commonjs modules, i.e. what do you get back when you In v15, the logic was simply to look for a key called 'default' on the module and, if found, return its value as the result of require(). In v16, @rollup/plugin-commonjs added another option for resolution behavior and made this configurable via a parameter called Now, call-bind is just such a module. It returns a default export, a function, but it ALSO attaches another function called From object-is/index.js
Because snowpack sets It seems to me that setting requireReturnsDefault to 'auto' with the switch to v16 probably just seemed like a sensible default and this change in behavior was unintended. Since snowpack 3.0.13, any project which includes I also commented on this in #3295 |
Beta Was this translation helpful? Give feedback.
-
@gpascale Thanks for your change. I'm not getting the |
Beta Was this translation helpful? Give feedback.
-
Snowpack has been awesome for building and serving our system, but after a recent update I'm completely stuck. The runtime appears to be looking for a hashed file name that doesn't match the files installed.
I've tried:
My
snowpack.config.js
-- it used to have more in it, but this still repro's the problem:Browser console error:
Error output from snowpack command:
(note that the hash of the file on disk doesn't match what snowpack is looking for).
Haalp?
Beta Was this translation helpful? Give feedback.
All reactions