Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading from 0.41 results in "Cannot read properties of undefined (reading ‘$$’)" #1427

Closed
NigelCunningham opened this issue Aug 6, 2022 · 3 comments · May be fixed by #991
Closed

Comments

@NigelCunningham
Copy link

Hi there.

I'm trying to upgrade my (previously working) project to use newer versions of the dependencies. I've been using Carbon components and am running into the above error message. I've done a fair bit of Googling, without success so far, but I have manged to make a set of minimal steps to reproduce the issue:

  1. With Meteor 2.7.3 (I'm using the git repo, on tag release/METEOR@2.7.3), run meteor create test --svelte
  2. meteor run
  3. meteor npm i --save carbon-components-svelte
  4. Edit imports/ui/App.svelte, adding:
    import { Button } from 'carbon-components-svelte';
  5. Modify button to Button in both places on line 14.

Things that I've tried:

  1. Update svelte to ^3.48 (https://github.com/carbon-design-system/carbon-components-svelte says it requires this)
  2. Downgrade carbon-components-svelte to 0.60 or 0.50, both without success.

The working version is using carbon-components-svelte 0.41.

I'm thinking the issue is in carbon-components-svelte because if I just upgrade carbon-components-svelte, that's what breaks my build. I can of course find the issue reported elsewhere, but not a solution that is helping in this case.

Can someone help, please? Thanks in advance!

@metonym
Copy link
Collaborator

metonym commented Aug 6, 2022

This seems like a similar error to #896.

Can you try the approach suggested in this comment?

@NigelCunningham
Copy link
Author

Thanks for the reply. Do I make that change in the package.json for this repo (do something like forking the repo and install my fork?)

@NigelCunningham
Copy link
Author

Yes, doing the above does the trick.

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

Successfully merging a pull request may close this issue.

2 participants