-
Notifications
You must be signed in to change notification settings - Fork 37
Make react/enzyme dependency soft #473
Conversation
Please add one of the following required labels:
|
1 similar comment
Please add one of the following required labels:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good to me so far, left a minor comment about removing the redbox-react dependency.
@@ -8,15 +8,7 @@ | |||
|
|||
/* eslint-env node */ | |||
|
|||
const React = require('react'); | |||
const RedBox = require('redbox-react').RedBoxError; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're getting rid of this, we should remove the redbox-react
dependency from package.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, good catch!
Please add one of the following required labels:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM assuming tests pass. Not seeing a very useful error stack in CI unfortunately =(
Currently fusion-cli depends on react and enzyme in order to be used at all. This was originally done to make it easier to test React, but the overall goal of fusion-cli is to be a CLI+compilation infrastructure that is agnostic of view libraries.
This PR allows fusion-cli to be installed and used without throwing react/enzyme-related errors, while still enabling them to be used if they're detected.