You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inspired by the discussion in this PR, we can remove the shared directory prefix to allow for cleaner manifests and easier usage. This would make the @bufferapp/static-assets library simpler and custom solutions to be cleaner as well.
Since most apps are never referencing ./public in their code, it makes sense to remove it, potentially by default. To do this we could:
Automatically remove the word public as a prefix directory
Check all file globs and remove any common base directory that is shared by all
Change the structure of the globs to be simpler or allow for a directory prefix input, ex. `buffer-static-upload -prefix public -files 'js/.js,css/.css'
Purpose
Inspired by the discussion in this PR, we can remove the shared directory prefix to allow for cleaner manifests and easier usage. This would make the
@bufferapp/static-assetslibrary simpler and custom solutions to be cleaner as well.Idea
Given a generated manifest:
{ "public/js/bundle.js": "https://static.buffer.com/my-app/public/js/bundle.123456789.js" }It would become:
{ "js/bundle.js": "https://static.buffer.com/my-app/js/bundle.123456789.js" }Since most apps are never referencing
./publicin their code, it makes sense to remove it, potentially by default. To do this we could:publicas a prefix directory