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.

Sign up for GitHub

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

Jump to bottom

Comment Out inline plugin, move to "external" folder inside project (same with loader). #16

Open
11 tasks
TheLarkInn opened this issue Oct 3, 2016 · 0 comments
Open
11 tasks

Comment Out inline plugin, move to "external" folder inside project (same with loader). #16

TheLarkInn opened this issue Oct 3, 2016 · 0 comments

Comments

@TheLarkInn
Copy link
Owner

Since there has been offered help to write a package test suite, I think it would be also great to teach developers who are writing these plugins and loaders how to write sturdy suites for them as well.

  • Comment out inline plugin (its a little confusing for first time users anyways but I think should still be there).
  • Plugin Suite
    • Move plugin to separate folder, with mono-repo style treatment, maybe even package.json
    • Add testing library (@sindresorhus 's ava would be fun since all async)
    • Write a few unit tests
    • Highlight ways to integration test with fixtures (actually running against a webpack build)
  • Loader Suite
    • Move loader into separate folder, with mono-repo style treatment, maybe even package.json
    • Update resolveLoader.alias to reflect movement/location
    • Write a few unit tests
    • Highlight ways to integration test with fixtures (actually running against build)
@TheLarkInn TheLarkInn mentioned this issue Oct 3, 2016
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TheLarkInn