Describe the feature you'd like to request

Want to be able to create NextJs v12.x application, instrumented with sentry-javascript v7.x on Vercel. With all the new features of both respectively. Including new features and fixes, listed in both release notes respectively.

Describe the solution you'd like

The with-sentry example application should be default latest version of NextJs

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. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions

Summary

The current latest version

💻

• 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

🐛 bug report

Live reloading on changes and HMR work as expected, until an HTML page includes a "classic" (non-module) script.

🎛 Configuration (.babelrc, package.json, cli command)

{
"browserslist": "> 0.5%, last 2 versions, not dead",
"devDependencies": {
  "parcel": "^2.5.0",
  "posthtml-expressions": "^1.9.0",
  "posthtml-extend": "^0.6.3",
  "posthtml-include": "^1.7.

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

I can't find any documentation or thorough tests of the path substitution performed by compiler/options/pathSubs.

From looking at the code, these are the substitutions:

• $nim: global nim prefix directory path
• $lib: stdlib directory path
• $home: user's home directory path
• $config: I think this is the directory path to the either the nimscript calling
  `compiler/options/path

Feature

Our set.update uses IterNext for iterating given args and update the set contents (makes sense).
But this makes incompatibility with cpython.
cpython's implementation is converting given args to tuple and uses get_size and get_item.
As these method does not go through the iternext, there is no exception if the set is mutated during update.

Python Documentation

h

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

• I have tried using the latest released version of Numba (most recent is
  visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
• I have included a self contained code sample to reproduce the problem.
  i.e. it's possible to run as 'python bug.py'.

I think I have discovered a very minor bug - or rather inconsistency with numpy - in Numba's implementation

I am interested in helping provide a fix!

No

Which generators are impacted?

• All
• Angular
• HTML
• Qwik
• React
• React-Native
• Solid
• Stencil
• Svelte
• Vue
• Web components

Reproduction case

https://codesandbox.io/s/hungry-cache-trlkvp

Expected Behaviour

in angular [style]="obj" should be [ngStyle]="obj" and in svelte is