Skip to content

feat: support specifying directory for static files and template sources via a new publicDir option #3836

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

Closed
wants to merge 2 commits into from

Conversation

kbtz
Copy link

@kbtz kbtz commented Apr 17, 2019

Adds a publicDir option to specify an alternative name or path to the public directory. Doc entry added and wording adjusted is some places to avoid confusion from the deterministic mentions to public/.

Tested locally both single and multi-page mode. If everything went alright I plan to work at #2697 later on.

@haoqunjiang
Copy link
Member

Thank you for your enthusiastic help but we have decided not to add this option. See more discussions here: #2436 (comment) #3040 (comment) #3061 (comment)

@kbtz
Copy link
Author

kbtz commented Apr 18, 2019

Thank you for gathering these comments, now I not only understand the decision but also agree with it!

I'm considering making those tweaks via cli plugin, but I couldn't find information regarding plugin interoperability. Could you help me get started and point what could I do to ensure that my plugin is the last one extending the webpack configuration?

@kbtz
Copy link
Author

kbtz commented Apr 21, 2019

Whops, forgot to mention you...
@sodatea ping

@haoqunjiang
Copy link
Member

Currently there's no way to do so.
Though, we do have plans to add a plugin ordering mechanism. We just haven't figured out a good API interface…

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.

2 participants