-
-
Notifications
You must be signed in to change notification settings - Fork 372
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
Unexpected token and octokit deprecation error #812
Comments
Interesting, do you have babel in your project? It might not be picking up the local copy and then won't be able to transpile your JS |
@orta we're on babel 7.20; could this have to do with:
in package.json? |
+1 for this. We still have old babel in our project, no resolutions.
|
The deprecation message is visible also on danger-swift's CI |
Just tried this with 7.0.9 and there're no more deprecation warnings but the syntax error is still there:
Any ideas on how to fix this? |
I think this is something to do with how the automatic babel setup is working on your project, try run |
@orta Thanks! The relevant output seems to be:
so it finds config but then ignores it? |
It seems after working with @kangax on this that regular node module imports work fine (like 'lodash', and 'danger'), but native imports like fs and path, it seems as though you have to use I will try to look into the danger code to see if there is anything I can do for a PR to fix this issue |
I'm running a simple example dangerfile.js straight from the docs, using the latest 7.0.2:
and
yarn danger local
throws both syntax error and deprecation notice:Am I missing something?
The text was updated successfully, but these errors were encountered: