Uh oh!
There was an error while loading. Please reload this page.
added code for sandpack console - #4672
Conversation
Size ChangesDetails📦 Next.js Bundle AnalysisThis analysis was generated by the next.js bundle analysis action 🤖
|
| Page | Size (compressed) |
|---|---|
global | 84.68 KB(🟡 +86 B) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
harish-sethuraman
commented
May 22, 2022
@danilowoz Seems like the new bundler doesn't emit |
Uh oh!
There was an error while loading. Please reload this page.
gaearon
commented
Jun 10, 2022
We need to keep the normal font for the "Console" header itself. Monospace is just for the content. |
gaearon
commented
Jun 10, 2022
And let's make the console hidden until the first |
Uh oh!
There was an error while loading. Please reload this page.
Adds console to sandpack component
UI :
Behaviour:
console.logonly. No errors or warnings.Object.prototype.toString.call(value). If that throws too, just print"[" + typeof(value) + "]".console.log("hi", {}, {})the vertical space between objects is too large. Put them closer. The excessive indentation is also strange, let's remove it.message.firstLoadfrom sandpack)console.loginto component body and then edit it causes to console to always clear before next render. I don't know why. Seems like a bug.