Compiler

Describe the feature you'd like to request

I want to be able to initialize a Next.js app with the src directory.

It is currently a hassle to create the src on your own and move pages and other folders to it.

Describe the solution you'd like

Add an option to create-next-app to be able to do that. Like: --src, `

Describe the problem

the low level documentation (https://svelte.dev/docs) is not really easy to use ( and incomplete in some cases)
I think if the runtime function contain JSDOC it will help a lot and give the developers an easier way to discover api documentation

additionally it is possible to replace the https://svelte.dev/docs with the generated docs ( with some thing like https://ty

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
• This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Description

If

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

visitors: {
    JSXElement(path) {
        console.log(path.generateUidIdentifierBasedOnNode(path.node));
        // logs `_objectObject`
    }
}

Configuration file name

No response

Configuration

No response

Current and expected behavior

Logs

Marked version:
3.x.x

Describe the bug
A clear and concise description of what the bug is.

Right now, import {use} from "markedjs" does not work, this worked in 2.x.x.

To Reproduce
Steps to reproduce the behavior:

Install & import it.
The DefinitelyTyped definitions also mark this incorrectly as being supported still.

A workaround is importing one of the structur

Describe the feature

Related with swc-project/swc#3859.

We want to establish initial feature parity to existing @swc/cli to plan out migration with possible breaking changes.

These are initial flags we'd like to have.

• config
• config_file
• filename (swc-project/swc#4016)
• env_name
• ignore

It is awkward, but TypeScript officially supports using .js in import specifiers, like so:

import {foo} from './path/to/some/file.js'
console.log(foo)

where ./path/to/some/file.js does not actually exist, but th

I expected ? to not overwrite the query, but to merge. The docs of the proc use the word "concatenate" which implies that this is how the proc should work, but the implementation overwrites the query instead of concatenating.

Example

import uri
let foo = parseUri("https://google.com/?page=10")
echo(foo ? {"test": "42"})

Current Output

https://google.com/?t

See e.g. #2570. Some of the unit tests there with "wrong error message" should be somewhat easy to fix - just correct the error message we have to match CPython's. Others might be trickier, since you'll need to add diagnostics to recognize bad syntax and give a more detailed error than "unexpected token". Also, I think around half of them could be fixed just by adding "invalid syntax" in the messa

Is your feature request related to a problem? Please describe

Very often, with working with conformance view, I work with different versions of the same compiler, all options are the same. Or I work with different C++ standards, with the same compiler and the same options (exception for this one). Or...

Right now, to add a new compiler in the conformance view, I have to start from an empty

Numba ignores any indices that are out of bounds for a given array shape. This behavior is present in both basic and advanced indexing.

import numpy as np
import numba

@numba.njit
def something():
    arr = np.ones((3,3))
    arr[100] = 0
    arr[:, np.array([2,3,5,100])] = 0
    return arr

print(something()) # Does not raise error, ignores the out of bound indices comp