Remove unnecessary dependencies from released NPM package#968
Conversation
c26e6cb to
33a8739
Compare
|
@tricknotes Can you please rebase on top of master. Then let's see the CI results. |
33a8739 to
b0697bb
Compare
|
rebased |
hmm..., some tests are timeouted :< |
b0697bb to
d888926
Compare
6aea232 to
fab1996
Compare
|
@justin808 |
|
This looks solid to me. @Judahmeek? |
|
Nice work. However, I think that |
It is necessary to inform yarn what current directory should destination root.
Without package.json in dummy app, yarn will search package.json in ancestral directories. And when running `yarn install <package-name>`, the package.json will be destructively changed.
These dependencies were injected by generator spec. They are unnecessary for released react-on-rails package.
react-on-rails no longer depends on react-redux. The template file that uses react-redux should be passed ESLint regardless its dependency.
|
Thanks for your review, @Judahmeek ! I think it may be a optional dependencies. Or I've misunderstand? |
30b4a9f to
cb35cc4
Compare
|
You're correct that it is an optional dependency. |
These dependencies are injected by generator spec.
However they are unnecessary for released react-on-rails package.
Even if the
dependenciessection is removed, it will back after$ rspec spec/react_on_rails/generators/install_generator_spec.rbis run.I think it is unexpected behavior.
So I removed these dependencies and fix specs.
@Judahmeek @justin808
Can you review this PR? It this a correct way?
This change is