Closed ogonkov closed 3 years ago
There's no parser.parse
in this package source code, so it's probably an issue with codeclimate's cli. Make sure to upgrade the CLI to the latest version since 0.72 is really old.
I'm getting the same issue when running the engine on CodeClimate and not through the CLI. It started today. I contacted CodeClimate support and will update if I get a workaround or explanation that might benefit other users.
Unfortunately, error on CodeClimate's build is less helpful:
•• Timing: .engineConfig: 0.341s
Error: parser.parse is not a function
See our documentation at https://docs.codeclimate.com/docs/stylelint for more information.
I fixed my issue by replacing Gitlab template with job it actually provides (from master
).
But then I replace it with simple bash script that run only on changed files, while CC runs on whole project and took 15 minutes instead of few seconds. Inline lint report is missing, but I plan to write custom formatter.
@davehenton Let's continue the discussion here since that PR is already merged and is not related to the problem.
What does parser.parse
do?
I added new entries to the rules.json but it's a valid JSON
:wave:
Hm.
Based on the output we're seeing, this parser.parse
error is occuring within the stylelint engine. Possibly within one of the dependencies. Does someone have an open source repo that reproduces the issue?
My CodeClimate builds starting passing 21 hours ago, and they pass for all open source builds I try now. CodeClimate support haven't responded yet, but they must have changed something on their end.
@leonelgalan They reverted the last update.
@maxjacobson Yes, it is happening with this engine.
What does parser.parse
do?
@leonelgalan Hi there, I'm with Code Climate. Could you point me to an open source repo which was exhibiting this bug? That would help get to the bottom of it, which will allow us to move forward again.
@gilbarbara Just to be clear, what I mean is that this parser.parse
error seems to be emanating from this engine, most likely from one of its dependencies. Unfortunately there's no stack trace printed so it's not clear where exactly it's coming from. I'm happy to help debug it if we have a public repo to reproduce it against.
@maxjacobson, it wasn't an open source project. As soon as I started setting one (today) I couldn't get it to fail. I contacted support and checked the option to give you access to my code if needed. So please feel free to do so.
I have no idea how to fix this since this only happens in codeclimate.com. The CLI works fine.
Anyway, I've released a new version: 2.3.0 (engine 13.7.2)
@maxjacobson I just ran into this issue (Parsing error: parser.parse is not a function
) with a very simple PR. You asked for an example of an open source repo which is exhibiting this bug. https://github.com/sockethub/sockethub/pull/325 -- Let me know if there's somewhere I could file a proper issue for this.
Hi @silverbucket -- I actually don't work at Code Climate anymore. Let me tag in @efueger to take a look. Best of luck!
Created an issue here (in case anyone comes along this thread) https://github.com/codeclimate/codeclimate-eslint/issues/512
This is off-topic for this repo, locking.
.codeclimate.yml
.stylelintrc
Couldn't get engine to work, it just throws error, that is not much helpful:
CodeClimate runs from default GitLab Community Edition 11.11.2
code_quality
template.