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

Use standard linter #4

Closed
doug-wade opened this issue Jul 31, 2017 · 0 comments · Fixed by #5
Closed

Use standard linter #4

doug-wade opened this issue Jul 31, 2017 · 0 comments · Fixed by #5

Comments

@doug-wade
Copy link
Collaborator

Static-file-loader follows JavaScript Standard style. To make it easier to accept outside contributions to the repository, while following the style, we should set up the standard linter, and run it as part of the test target.

doug-wade added a commit to doug-wade/static-file-loader that referenced this issue Jul 31, 2017
doug-wade added a commit that referenced this issue Sep 2, 2017
[#4] Set up the standard linter on CI
Bobgy pushed a commit to Bobgy/static-file-loader that referenced this issue Apr 15, 2018
einzige added a commit to starcling/static-file-loader that referenced this issue Feb 25, 2021
* [kossnocorp#4] Set up the standard linter on CI

* [kossnocorp#9] Standardize watch tasks

* Promote to v0.5.0

* Fix unit test command.

* upgrade webpack, file-loader dependency

* fix integration test with webpack 4 api and improve error reporting

* fix loader syntax with webpack 4

* fix integration test

* add webpack 4 as peer dependency

* code clean up && remove node 4 support in travis

* update readme

* v0.6.0

* Don't strip // from https:// publicPath

Co-authored-by: Doug Wade <dwade@indeed.com>
Co-authored-by: Douglas Wade <douglas.b.wade@gmail.com>
Co-authored-by: Sasha Koss <koss@nocorp.me>
Co-authored-by: Yuan Gong <yuan@indeed.com>
Co-authored-by: Sergey <sergeyshishkalov@gmail.com>
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 a pull request may close this issue.

1 participant