[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

Sublime 4149 generates "Error loading syntax file[...]: no such target" pop-up for "JavaScript (Babel)" #427

Closed
nabijaczleweli opened this issue May 4, 2023 · 3 comments
Closed

Sublime 4149 generates "Error loading syntax file[...]: no such target" pop-up for "JavaScript (Babel)" #427

nabijaczleweli opened this issue May 4, 2023 · 3 comments

Comments

@nabijaczleweli
Copy link

And, indeed, I see a

            -   - meta_include_prototype: false
                - match: ''
                  set: scope:source.js.css#at-keyframe-block-content
                  with_prototype:
                    - match: (?=`)
                      pop: true
                    - match: \$\{
                      scope: punctuation.section.interpolation.begin.js
                      push:
                        - clear_scopes: 1

block, and this is the only mention of this in the package.
@Thom1729
Copy link
Contributor
Thom1729 commented May 4, 2023

I'm on vacation, but I should be able to look into it later today. My initial guess is that there's a mismatch between the version of the Styled Components syntax in JS Custom and babel-sublime. If so, the proper fix would be to update that syntax. (It's possible that the script I use to update babel-sublime from JS Custom doesn't catch that file, in which case I should fix that as well.)

It's also possible that recent changes to the core CSS syntax broke the Styled Components extension. I have not looked into this at all but I vaguely recall hearing about changes to that syntax.

It could also be something completely different.

@Thom1729 Thom1729 mentioned this issue May 5, 2023
Closed
@Thom1729
Copy link
Contributor
Thom1729 commented May 5, 2023

Since it seems to be broken upstream in JS Custom as well, it's probably a breaking change to the core CSS syntax.

@Thom1729
Copy link
Contributor

Fixed in v11.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nabijaczleweli @Thom1729