-
Notifications
You must be signed in to change notification settings - Fork 1
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
Small problems at using #65
Comments
About the validation, please read this documentation: https://github.com/gflohr/e-invoice-eu/blob/main/contrib/validators/README.md You should definitely validate your invoices before sending them. It is very unlikely that they are correct from the beginning. I will take care of the other two problems next week. I am currently travelling. |
add missing backslash See #65, issue a), thanks to @ralfdreibrodt.
Until I fix the other two issues, you may consider to use the containerized version on dockerhub. |
Fixed. |
Sorry, my bad, you can not move the directory. |
I cannot reproduce the reference error for |
Thank you for your changes. The documentation is now correct.
It still does not work, but the error message changed. Btw this is a Debian 12.
|
I could reproduce the issue with node 18. It should now work with node 18, 20, and 22. Can you try again? |
Thank you, it is working now! |
Thank you for reporting the problems! |
I had three problems during installation and creating my first invoice:
a) "Full-Fledged Example" from README:
In line three the backslash is missing
b) https://www.guido-flohr.net/creating-electronic-invoices-with-free-and-open-source-software/
This will create a directory dist that you can copy wherever you like.
Whenever I move the dist directory, I get an error:
Without moving dist it is working, until:
c) changing the format to Factur-X-XRechnung
The software is crashing:
After googling the error message, I added before the above line 239 this:
const crypto = require('crypto');
Now the software is not crashing anymore and the validator says everthing is correct, but I have no idea, whether that's true.
The text was updated successfully, but these errors were encountered: