-
-
Notifications
You must be signed in to change notification settings - Fork 19
New Install required regenerator-runtime which is not in configuration or installation readme #61
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
Comments
Thanks for opening this issue!
|
Which version of the mail adapter are you using? There is no version 6.x. Were you able to track down what exactly causes the error, or which part of the adapter requires that dependency? |
sorry, It's version 2.1.0 this is the exact error I get.
dependencies in package.json
I hope that helps. I didn't look into ApiMailAdapter.js yet as installing the regenaratorRuntime in package.json and requiring it in my app.js worked for me. |
It seems that the polyfill that babel generated requires runtime, which Node version did you run this on? Maybe helpful for further investigation: https://stackoverflow.com/a/56754212/1870795 |
i have v16.15.0 running. So you don't encounter this problem with a new install on your end @mtrezza ? |
We have a CI that tests with Node 16 and tests pass. Do you still see this issue in the latest version? |
I just ran into this issue here: Solution/Workaroundyarn add regenerator-runtime in index.ts (or where ever): |
@penchef Which Node version are you using? It's not clear at this point what requires |
maybe this helps: I only ran into this when I was running tests. This is the stack trace of the error:
Node: v18.14.2 |
What do you see at node_modules/parse-server-api-mail-adapter/lib/ApiMailAdapter.js:155:56? |
I have just commented out the regeneratorRuntime dependency in my package.json and so far it seems to be working fine. |
Hi,
|
Maybe this: parcel-bundler/parcel#1762 (comment), or remove babel altogether from this repo. |
Could you please try out version 4.0.0? It rebuilds the package-lock file, so maybe it fixed this issue. |
Can confirm, 4.0.0 is working great, thanks! |
Closed via #94 |
New Issue Checklist
Issue Description
Going through the installation instructions from the README file, I get an error
ReferenceError: regeneratorRuntime is not defined
Which can be solved by requiring regenerator-runtime.
A quick update to the readme file requiring and installing regenerator-runtime fixes this.
Steps to reproduce
New installation on a clean parse-server will produce this issue.
Actual Outcome
error
ReferenceError: regeneratorRuntime is not defined
Expected Outcome
ReadMe should mention the requirement for regenerator-runtime for people not as tech savvy like I am.
Failing Test Case / Pull Request
Environment
6.0.1
5.2.1
Logs
The text was updated successfully, but these errors were encountered: