Skip to content
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

chore(default): migrate #394

Merged
merged 1 commit into from
May 14, 2019
Merged

chore(default): migrate #394

merged 1 commit into from
May 14, 2019

Conversation

alexander-akait
Copy link
Member

What kind of change does this PR introduce?

refactoring

Summary

  • azure pipelines
  • refactor test on import/export
  • update deps
  • move configurations to own files
  • commitlint + husky + lint-staged

Does this PR introduce a breaking change?

No

Other information

No

@codecov
Copy link

codecov bot commented May 13, 2019

Codecov Report

Merging #394 into master will increase coverage by 0.17%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #394      +/-   ##
==========================================
+ Coverage   96.86%   97.03%   +0.17%     
==========================================
  Files          13        7       -6     
  Lines         287      304      +17     
  Branches       83      103      +20     
==========================================
+ Hits          278      295      +17     
  Misses          9        9
Impacted Files Coverage Δ
lib/fs.js 95% <0%> (-1.08%) ⬇️
lib/util.js 100% <0%> (ø) ⬆️
test/fixtures/server-test/webpack.array.config.js
...xtures/server-test/webpack.client.server.config.js
test/fixtures/server-test/webpack.config.js
...fixtures/server-test/webpack.querystring.config.js
index.js 97.67% <0%> (+0.17%) ⬆️
lib/middleware.js 94.91% <0%> (+0.27%) ⬆️
lib/context.js 95.55% <0%> (+0.55%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 762efe4...9c36a30. Read the comment docs.

rules: {
'prettier/prettier': ['error'],
strict: ['error', 'safe'],
strict: ['off'],
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need migrate on babel in next PR

@alexander-akait
Copy link
Member Author

alexander-akait commented May 13, 2019

npm audit works very bad 😞

package.json Outdated
"test": "jest",
"release": "standard-version"
"test:watch": "jest --watch",
"test:coverage": "jest --collectCoverageFrom='lib/**/*.js' --coverage",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to create jest.config.js like webpack-dev-server.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need do same in webpack-default and here

@@ -0,0 +1,136 @@
# Contributing in @webpack-contrib
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- @webpack-contrib
+ webpack-dev-middleware

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is org, let's use webpack

@@ -0,0 +1,136 @@
# Contributing in @webpack-contrib

We'd always love contributions to further improve the webpack / webpack-contrib ecosystem!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- webpack-contrib
+ webpack-dev-middleware

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here means thanks fro contributing and in webpack and in webpack ecosystem

@hiroppy
Copy link
Member

hiroppy commented May 13, 2019

@evilebottnawi Can you add renovate to this repository?

@alexander-akait
Copy link
Member Author

@hiroppy What we should do here to enable this?

"test": "jest",
"release": "standard-version"
"test:coverage": "npm run test:only -- --coverage",
"test:watch": "npm run test:only --watch",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/cc @hiroppy watch should be without coverage, so better use test:only (we need fix it in webpack-dev-server)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

watch should be without coverage

hm... honestly, I want to be able to see coverage when running as test:watch.

@alexander-akait
Copy link
Member Author

/c @hiroppy fixed

hiroppy
hiroppy previously approved these changes May 13, 2019
Copy link
Member

@hiroppy hiroppy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubber-stamp LGTM, Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants