-
Notifications
You must be signed in to change notification settings - Fork 88
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
● Validation Warning #2228
Comments
Hi there! It looks like your issue requires a minimal reproducible example, but it is invalid or absent. Please prepare such an example and share it in a new issue. The best way to get attention to your issue is to provide a clean and easy way for a developer to reproduce the issue on their own machine. Please do not provide your entire project, or a project with more code than is necessary to reproduce the issue. A side benefit of going through the process of narrowing down the minimal amount of code needed to reproduce the issue is that you may get lucky and discover that the bug is due to a mistake in your application code that you can quickly fix on your own. ResourcesCommon concerns"I've only been able to reproduce it in private, proprietary code"You may not have spent enough time narrowing down the root cause of the issue. Try out the techniques discussed in this manual debugging guide to learn how to isolate the problem from the rest of your codebase. "I didn't have time to create one"That's understandable, it can take some time to prepare. We ask that you hold off on filing an issue until you are able to fully complete the required fields in the issue template. "You can reproduce it by yourself by creating a project and following these steps"This is useful knowledge, but it's still valuable to have the resulting project that is produced from running the steps, where you have verified you can reproduce the issue. |
Hi there, repro would be useful for us to help us understand what's happening better. Also, please stick to the issue template we have set up in this repo. |
If you want to ask questions in a more loosely structured form, you can do so at https://chat.expo.dev/ |
Unknown option "serializer.isThirdPartyModule" with value (module) =>
/(?:^|[/\])node_modules[/\]/.test(module.path) was found.
This is probably a typing mistake. Fixing it will remove this message.
● Validation Warning:
Unknown option "symbolicator.customizeStack" with value async (stack, _) => stack was found.
This is probably a typing mistake. Fixing it will remove this message.
● Validation Warning:
Unknown option "watcher" with value {"additionalExts": ["cjs", "mjs"], "healthCheck": {"enabled": false, "filePrefix": ".metro-health-check", "interval": 30000, "timeout": 5000}, "unstable_workerThreads": false, "watchman": {"deferStates": ["hg.update"]}} was found.
This is probably a typing mistake. Fixing it will remove this message.
● Validation Warning:
Unknown option "unstable_perfLoggerFactory" with value () => {
class Logger {
start() {}
end() {}
annotate() {}
point() {}
subSpan() {
return this;
}
}
return new Logger();
} was found.
This is probably a typing mistake. Fixing it will remove this message.
Can anyone help me to figure out this error to start metro for React Native CLI
Originally posted by @sbhakat1 in expo/expo#23213 (comment)
The text was updated successfully, but these errors were encountered: