Conversation
|
Please forgive me for my ignorance in the matter, but I couldn't find any relevant Issues. Outside of avoiding errors when the user has another version of |
|
@wtgtybhertgeghgtwtg we'll be For now we're starting with webpack because it's the easiest way to start off this bundling work. |
|
Sorry if I wasn't clear, I meant for a project using Depending on what you end up bundling, this might occur in |
|
@wtgtybhertgeghgtwtg Next.js will get security warnings from GitHub's analysis of There's a major security benefit from compiling into a standalone bundle (the same way that yarn does), which is that no nested "unpinned" dependencies that the Next.js team doesn't know about get installed. So, we forego |
That works for
It'll avoid shipping versions that have a known vulnerability, but that doesn't mean that vulnerabilities cannot be discovered for the existing version it is using. |
Stats from current PRClick to expand stats
Click to expand serverless stats
|
Stats from current PRClick to expand stats
Click to expand serverless stats
|
SingleEntryPlugin for dev addEntry
Stats from current PRClick to expand stats
Click to expand serverless stats
|
Stats from current PRClick to expand stats
Click to expand serverless stats
|
Stats from current PRClick to expand stats
Click to expand serverless stats
|
This will bundle
webpackwithnextusingncc