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

create a general purpose copy mechanism like what is being used for assets/ directory copy #543

Closed
1 of 5 tasks
thescientist13 opened this issue Apr 11, 2021 · 1 comment · Fixed by #738
Closed
1 of 5 tasks
Assignees
Labels
alpha.0 CLI documentation Greenwood specific docs Plugins Greenwood Plugins v0.17.0
Milestone

Comments

@thescientist13
Copy link
Member

Type of Change

  • New Feature Request
  • Documentation / Website
  • Improvement / Suggestion
  • Bug
  • Other (please clarify below)

Summary

Not sure if this would just be a configuration like:

// _greenwood.config.js_
module.exports = {
  copy: [
    'some/path/a/',
    'some/path/b/,
  ]
}

Details

Something like the webpack plugin, and would be the same we would use internally as part of the build command.

@thescientist13 thescientist13 added documentation Greenwood specific docs CLI labels Apr 11, 2021
@thescientist13 thescientist13 added this to the 1.0 milestone Apr 11, 2021
@thescientist13 thescientist13 self-assigned this Sep 27, 2021
@thescientist13 thescientist13 added the Plugins Greenwood Plugins label Sep 27, 2021
@thescientist13
Copy link
Member Author

Saw some "build shenanigans" related to copying files for the polyfills plugin, and in fairness / self deprecation, is a pretty inefficient way of copying these files, so this is me considering self-escalating the priority of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alpha.0 CLI documentation Greenwood specific docs Plugins Greenwood Plugins v0.17.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant