-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Linking master branch for local development #104
Comments
You can't simply link anything that has a build process. You'll need to run |
Running mparker:~/Documents/Dev/chai-enzyme (master) $ npm link
> chai-enzyme@0.5.1 prepublish /Users/mparker/Documents/Dev/chai-enzyme
> npm run clean && npm run build
> chai-enzyme@0.5.1 clean /Users/mparker/Documents/Dev/chai-enzyme
> rimraf build
> chai-enzyme@0.5.1 build /Users/mparker/Documents/Dev/chai-enzyme
> babel src --out-dir build
|
However, that won't install dev dependencies - but sure, if you already have them installed you'll be all set. Is there anything about your test suite that might be transpiling things in node_modules for you? |
My test suite (mocha) uses babel-register. I thought that only transpiled my test files. Does that affect node_modules too? |
Yes, |
Okay, but I still don't understand why this would affect local development. |
Hi all,
I was interesting in taking a look at this library to see how it works and if I was able to help contribute, so I decided to pull it down and link my codebase to use the local version of
chai-enzyme
.After doing this and running my test suite, every single test that uses
chai-enzyme
assertions fails.And so on. It looks like
wrapper
is undefined inassertions/tagName.js
,assertions/className.js
,assertions/generic.js
, etc. After unlinking and pulling the latest version down from npm, these failures go away.So I guess my question is, am I doing something wrong here? Why do my tests fail when I link to
chai-enzyme
from a local folder?The text was updated successfully, but these errors were encountered: