-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[TextField] "ReferenceError: process is not defined" #1486
Comments
TextField is not the only component which has this issue. I just found FloatingActionButton also has the same issue. |
Well... this project was designed from ground up to be bundled. All these checks must follow the rule: |
The usage of |
Is there any chance of this being fixed in the future? There are now alternatives to react that work fully in the browser such as preact, and it would be really nice to use material-ui with preact |
@Yamboy1 We have a best effort to support preact. If you can reproduce the issue with the latest version v5.0.0-alpha.5, please open a new issue. A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you! |
Bumps [wait-on](https://github.com/jeffbski/wait-on) from 3.3.0 to 4.0.0. - [Release notes](https://github.com/jeffbski/wait-on/releases) - [Commits](jeffbski/wait-on@v3.3.0...v4.0.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
When TextField component is used in browser environment, calling method 'setErrorText' causes "ReferenceError: process is not defined". In the sources of material-ui this method implemented this way:
link to source
It figures out that 'process' is global variable which is defined in Node.js environment, but obviously absent in browser. Implementation must first check that 'process' variable is set, but it does not. I looked through another sources and found many cases like this.
The problem can be solved by manually defined dummy 'process' variable, but IMHO this must be fixed in library.
Hack to workaround this problem:
The text was updated successfully, but these errors were encountered: