-
Notifications
You must be signed in to change notification settings - Fork 23
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
Illegal char <:> at index 4: node:internal/modules/cjs/loader:936 #73
Comments
Do you get the same error when you run from the commandline? If so can you run with Line 47 in db63697
|
|
FYI just adding our own node and yarn3 and running prettier ourselves with prettier-plugin-java works fine |
If you run this command directly what does the output look like? And then what if you convert all the forward slashes to backslashes? For example: |
If we can get the args right so that one of these direct calls works (without Maven), it should be pretty straight-forward to update the plugin code to generate that same invocation |
Interestingly, the bin-prettier file does not exist and the error is quite different:
It seems maven has a second problem of trying to parse |
Does |
Can you try deleting that folder, re-running the Maven plugin from the commandline, and seeing if it gets recreated with some actual files inside? |
Sorry for the delay. prettier-plugin-java is downloaded using npm install: Lines 47 to 49 in 938f2be
|
Not sure if this is an issue for this repo or for jhipster/prettier-java. I just tried setting up this plugin in our project, and all my attempts to run it yield this error message:
I took the config from your readme, removed what I didn't need, and tried updating the versions too. I also noticed using the implicit default inputGlobs yields paths with mixed forward and backward slashes (windows) in
print-args
, specifying the inputGlobs as per the readme makes them consistent. I thought the backslashes might be causing the syntax error, but apparently that's not it.Any advice or help, please?
The text was updated successfully, but these errors were encountered: