You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dynamic require calls like this one (where the module identifier string is not a string literal) are not supported in client-bundled code, because it's hard/impossible to know at bundling time exactly what module is being imported.
Webpack works around this by including all modules matching a certain configuration option, but then you're potentially shipping unused modules to the client.
You can force certain specific modules to be included in the bundle by putting
require("react-jsonschema-form/lib/components/fields/SchemaField.js")
explicitly in your own code. Repeat for any other modules that might be imported by dynamic require calls at runtime.
The code in question appears to have been added two days ago, so I think this error was introduced by the release of [email protected], not by the recent Meteor release.
The text was updated successfully, but these errors were encountered:
dulguun0225
changed the title
0.40.0 introduced some issues in Meteor
0.41.0 introduced some issues in Meteor
Nov 9, 2016
* Update dependencies to their latest versions. (#386)
* Fix#385: Avoid dynamic requires. (#387)
* Fix#365: Tab stop for Add button + (#392)
* Add a single field form example in the playground (#390)
* Allow using field names containing a dot character (#397)
* Updated eslint config.
* Improve checkbox and radio button styles (#403)
* Add missing proptype for disabled (#416)
* Temporary fix for #349 and facebook/react#7630 radio widget bug (#423)
meteor/meteor#8035
Dynamic require calls like this one (where the module identifier string is not a string literal) are not supported in client-bundled code, because it's hard/impossible to know at bundling time exactly what module is being imported.
Webpack works around this by including all modules matching a certain configuration option, but then you're potentially shipping unused modules to the client.
You can force certain specific modules to be included in the bundle by putting
require("react-jsonschema-form/lib/components/fields/SchemaField.js")
explicitly in your own code. Repeat for any other modules that might be imported by dynamic require calls at runtime.
The code in question appears to have been added two days ago, so I think this error was introduced by the release of [email protected], not by the recent Meteor release.
The text was updated successfully, but these errors were encountered: