Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Static asset in-lining #1944
These users have a perfectly legitimate use case and I believe we should handle it.
There are many imaginable use cases for this, and have been a huge amount of issues we've responded to with a
referenced this issue
Apr 22, 2017
i really want this, but i'm not sure how to do it effectively. i see a few options:
i'm liking the 3rd option. thoughts?
i suppose we could do that, @Timer, it just feels a little funky to not use webpack for the single source of asset aggregation. even tho i love node, seeing
i'm not powerfully swayed one way or the other, but continuing to use webpack + an ENV var feels like it may render less friction
While debate continues on this, you can use raw-loader today without ejecting or forking with:
/* eslint import/no-webpack-loader-syntax: off */ import QuickStart from '!raw-loader!./Sections/QuickStart.md';
I know this isn't recommended, but I find an explicit binding to Webpack to be more palatable than eject or forking. Feels like a tradeoff between trouble caused by some hypothetical future state where CRA no longer uses Webpack and trouble now maintaining my fork or falling behind on updates to key pieces of the setup.