Mark the peer dependencies as dev dependencies too.

[lijunle]

/cc @LinusU

[LinusU]

Isn't the accepted practice that you include your dependencies peer-dependencies as your own dependencies? That is, just adding them as dependencies...

Also, I had a warning about eslint-plugin-react being an unmet peer dependency as well. Maybe that should go on the list also...

[lijunle]

We do not use eslint-plugin-react in our code. That one is fine to let it leave.

Not everybody use typescript and SASS parser, to whom use them, they will install typescript and SASS parser at project level. That is exactly how peer dependency works.

I have ideas to resolve these failing tests. The idea is to mark them as dev dependencies and peer dependencies.

[codecov-io]

Current coverage is 96.12%

Merging #125 into master will not affect coverage as of 2bc0442

@@            master    #125   diff @@
======================================
  Files           23      23       
  Stmts          439     439       
  Branches        85      85       
  Methods          0       0       
======================================
  Hit            422     422       
  Partial          9       9       
  Missed           8       8       

Review entire Coverage Diff as of 2bc0442

Powered by Codecov. Updated on successful CI builds.

[LinusU]

Ignore my stupid comment, I thought that it was peer dependencies to one of our dependencies 😆

[lijunle]

Actually, they are. We depends on their parse function to parse .ts (Typescirpt) files, .sass and .scss (SASS) files. However, I don't want to install everything then the user only use plain JavaScript.