-
-
Notifications
You must be signed in to change notification settings - Fork 865
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
Deprecation warning after running the development server #1496
Comments
I also see this warning. @palisadoes, can you please assign this issue to me once its approved |
@aarishshahmohsin The Same has been reproduced but It's working fine with the latest version of nodejs |
Thanks for assigning me the isse, I will quickly resolve it |
This is an issue with react-scripts dependency. We can solve this issue by manually changing a config file within react scripts, |
If you have a solution, please open a PR |
The solution requires me to modify the node_modules. That's the point |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Unassigning due to no activity or PR. |
Can I work on this issue, Pls assign it to me |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Unassigning due to no activity or open PR. |
Can I get assigned to the issue. |
Is this issue still persist, if it is there then I would like to take on this task? |
@rohansx I am still seeing the deprecated warning, do you see it when you start talawa-admin? |
Hey @Cioppolo14 I want to work on this issue. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Hi Can I get this issue assigned |
Hey @dhruvgupta0503 I have already created a PR. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
unassigning. no activity |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
can i work on this issue? plz assign me.I would love to work on it. |
Describe the bug
When the command
npm run serve
is executed to run the dev server, deprecation warnings are shown.To Reproduce
Steps to reproduce the behavior:
npm run serve
Expected behavior
There should be no warnings
Actual behavior
'onAfterSetupMiddleware' and 'onBeforeSetupMiddleware' are deprecated
Screenshots
![image (copy 1)](https://private-user-images.githubusercontent.com/49566965/299641134-4e65f63f-eb54-45a2-a2d3-f87aa9cf8b74.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5Mzc4ODcsIm5iZiI6MTczODkzNzU4NywicGF0aCI6Ii80OTU2Njk2NS8yOTk2NDExMzQtNGU2NWY2M2YtZWI1NC00NWEyLWEyZDMtZjg3YWE5Y2Y4Yjc0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDE0MTMwN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQxMjhlOThhMjRhOThmODM4OTk1N2IyYWM0MjU0MWQwZmQ0YTJiZjFlMGE2MjlkMDQ2MTY4NzM3MTQ4YjI4NzQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.FQmLgdT5Up4IKctKvIkxekCPptIchHIntZ_CGzKX4A0)
Additional details
The text was updated successfully, but these errors were encountered: