Compiler

What version of Next.js are you using?

11.1.0

What version of Node.js are you using?

14

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

Other (serverless aws)

Describe the Bug

When importing images into _document next does not emit these image assets into the client build.

For example, I

Describe the bug
The content of the the svelte file is a large HTML chunk, without any script logic or styling being involved. Max stack size exceeded error while compiling.

To Reproduce
https://svelte.dev/repl/a9dfcc17551c4aeb95e8fe748a97061d?version=3.20.1

Expected behavior
Compiling should not break

Information about your Svelte project:
Svelte 3.20.1, Rollup, Windo

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

type FuncWithDescription = [
  function: (...args: any[]) => any,
  string: string
]

https://babeljs.io/repl#?browsers=defaults&build=&builtIns=false&corejs=3.6&spec=false&loose=false&code_lz=C4TwDgpgBAYgrgOwMYHUCWwAWARCBnJAJzTGDQHsEoBeKAbQCgooAzRJMygLigAoA

Describe the bug
I'm using rollup to bundle dependencies (for a Svelte framework web app) but having trouble importing and using markedjs. It appears the library was recently ported to ESM modules, but I don't see any documentation on how to use as such. The standard syntax to import ES6 modules give me errors:

import { marked } from 'marked.esm';
returns
(!) Unresolved dependencies

Currently this works:

const obj = {
  foo: (...) => {...}
} as SomeClass

but this doesn't:

const obj = {
  foo(...) {...}
} as SomeClass

### Example
let unreachableProxy = "http://127.0.0.1:8888"
try:
  let client = newHttpClient(proxy=newProxy(unreachableProxy), timeout=1)
  var res = client.getContent("https://github.com")
  echo res
except:
  echo "Timed out"

Current Output

timeout variable is ignored, program stuck until default socket timeout will happen

Expected Output

Timed out a

Describe the bug
While reading https://github.com/compiler-explorer/compiler-explorer/blob/main/static/panes/conformance-view.js, I noticed that the skipAsm is misplaced in https://github.com/compiler-explorer/compiler-explorer/blob/a2a73953d6a23eaaab9ac724b7947317dc6e4471/stat

I see comments suggesting adding this to understand how loops are being handled by numba, and in the their own FAQ (https://numba.pydata.org/numba-doc/latest/user/faq.html)

from llvmlite import binding as llvm
llvm.set_option('','--debug-only=loop-vectorize')

You would then create your njit function and run it, and I believe the idea is that it prints debug information about whether