Skip to content

Using default custom path for files #3082

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

Merged
merged 1 commit into from
Aug 17, 2021

Conversation

guillaumebriday
Copy link
Member

Using https://webpack.js.org/guides/asset-modules/#custom-output-filename

It also fixes fonts that were extracted in media/images.

@guillaumebriday guillaumebriday requested a review from dhh July 6, 2021 13:35
@guillaumebriday
Copy link
Member Author

cc @justin808

@dhh dhh merged commit b64434d into rails:master Aug 17, 2021
@guillaumebriday guillaumebriday deleted the feature/file-static branch August 17, 2021 14:04
- Webpacker's wrapper to the `splitChunks()` API will now default `runtimeChunk: 'single'` which will help prevent potential issues when using multiple entry points per page [#2708](https://github.com/rails/webpacker/pull/2708).
- Changes `@babel/preset-env` modules option to `'auto'` per recommendation in the Babel docs [#2709](https://github.com/rails/webpacker/pull/2709)
- Adds experimental Yarn 2 support. Note you must manually set `nodeLinker: node-modules` in your `.yarnrc.yml`.
- Fixes dev server issues [#2898](https://github.com/rails/webpacker/pull/2898)
- Update static files path to from `media/` to `static/`.
Copy link
Contributor

Choose a reason for hiding this comment

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

@guillaumebriday @tomdracz, did this require some change to the upgrade docs? was this a breaking change?

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.

3 participants