Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Formik cannot be built from source

See original GitHub issue

Bug, Feature, or Question?

I’m trying to include Formik in my bundle with Webpack. However, Formik appears to bundle prop-types, invariant, warning, and a few lodash modules, even if they are present in my bundle. Is this by design? I don’t want to ship multiple copies of these shared libraries.

Current Behavior

Formik bundles certain required libraries

Desired Behavior

Formik requires these libraries as dependencies rather than bundling directly

Additional Information

Formik is great, and I really like using it 😃

Formik Version: 0.11.11
React Version: 15.3
TypeScript Version: n/a
CodeSandbox Link: n/a
OS: OSX 10.12.6
Node Version: 8.10
Package Manager and Version: npm@5.6

Issue Analytics

State:
Created 6 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

prichodkocommented, Mar 14, 2018

Actually, I haven’t noticed it until this PR came - https://github.com/jaredpalmer/formik/pull/513, when creating ESM or CJS bundles, I believe they should not include any external dependencies, because bundlers can handle that.

There is a comment from @Andarist https://github.com/rollup/rollup/issues/1847#issuecomment-356644324 and also his blog post - https://developers.livechatinc.com/blog/how-to-create-javascript-libraries-in-2018-part-2/

0reactions

jaredpalmercommented, Mar 14, 2018

I cut a release with the new build setup. Try formik@next or formik@1.0.0-alpha.3