Skip to content
This repository has been archived by the owner on Jan 14, 2024. It is now read-only.

I'm getting "TypeError: e.forEach is not a function" thrown in my console #29

Closed
MSeneadza opened this issue Mar 17, 2023 · 5 comments
Closed

Comments

@MSeneadza
Copy link

I swapped Tachyon for instant.page on my site and I'm seeing this in my console:

Uncaught TypeError: e.forEach is not a function
    at tachyon.min.js:1:593
    at Array.forEach (<anonymous>)
    at MutationObserver.observe.childList (tachyon.min.js:1:580)

you can see it live here https://swingtradebot.com/stocks-tagged-as/38592-inverse-etf

@cowtoolz
Copy link
Owner

cowtoolz commented Mar 18, 2023

Are you running tachyon with <script ... defer>? I'd appreciate you posting more details when you're able (how you're deploying tachyon and in what cases you're getting the error). I'll look into this tomorrow afternoon. Hope you're enjoying your St. Paddy's day, and glad to see you're also from Atlanta 🙌

@MSeneadza
Copy link
Author

Oh, how cool that you're also in Atlanta!

Yes, I just copied the script tag from the README (and converted it to HAML) and pasted it into the footer of my site's layout. (I tried it in the head section and go the same result.) Here's what I just copied from viewing source on my site:

<script crossorigin='' defer='defer' integrity='sha384-mWEnITn0upRV8CTm3KnqWW5XKFt7bnWaT6RBKBRIcCPyZx9dxqbAH56ew8NwOTgN' src='https://unpkg.com/[email protected]/tachyon.min.js' type='module'></script>
 
It's a Ruby on Rails app & the error seems to appear on every page load on all pages of my site.

@MSeneadza
Copy link
Author

BTW, I tried it on another Rails app of mine, which has much simpler pages and I get the same results. You can see that here https://sharesdb.com

@nikrowell
Copy link

nikrowell commented Mar 19, 2023

Hey Guys -
Fun fact - I was just in Atlanta last weekend 😀 and OMG Buttermilk Kitchen!

I had 1.1.0 on a local project and just tried switching over to 1.1.2 and am seeing the same error as @MSeneadza
Let me know if I can help with troubleshooting in any way.

Cheers!

@cowtoolz
Copy link
Owner

Thanks for the help, guys- accidentally missed a tiny detail pushing out the 1.1.2 release. 1.1.3 includes the relevant fix. Going to start writing a test suite so this doesn't happen again...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants