Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C create-react-app
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,547
    • Issues 1,547
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 417
    • Merge requests 417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • create-react-app
  • Issues
  • #5172
Closed
Open
Issue created Sep 29, 2018 by Administrator@rootContributor

Runtime chunk inlining and asset manifest

Created by: gaearon

Took me a bit to figure out what this is about, but I guess it's saying that they have a script which goes over each file in asset manifest (e.g. to add a <script> for it to a custom HTML page template), but runtime chunk is not there.

I wonder how we could handle it. I guess folks who use asset manifest (e.g. Django integrations and similar) won't read the runtime chunk from our HTML. So it'll be broken anyway.

Should we both emit runtime chunks and inline it? Normally it gets unused but folks who read the manifest get a separate script.

Assignee
Assign to
Time tracking