Module parse failed: Unexpected character '�' (1:0)

Is there an existing issue for this?

[X] I have checked for existing issues https://github.com/getsentry/profiling-node/issues
[X] I have reviewed the documentation https://docs.sentry.io/
[X] I am using the latest SDK release https://github.com/getsentry/profiling-node/releases

How do you use Sentry?
Sentry Saas (sentry.io)
SDK Version
1.0.7
Link to Sentry event
No response
What environment is your node script running in?

Next.js 13 app using App Directory, using "@sentry/nextjs": "^7.57.0"
MacOS Ventura 13.4.1 (22F82)
Node v18.12.1

How is your code deployed and bundled?
Standard Next.js build process running on Vercel. Here's the abstracted next.config.js:
import { withSentryConfig } from '@sentry/nextjs';

/** @type {import('next').NextConfig} */
const nextConfig = {
  async rewrites() {
    return [
      {
        source: '/api/sentry/:path*',
        destination:
          'https://{x}.ingest.sentry.io/api/{y}/envelope/',
      },
    ];
  },
  sentry: {
    hideSourceMaps: true,
    tunnelRoute: '/api/sentry',
  },
};

/** @type {import('@sentry/nextjs').SentryWebpackPluginOptions} */
const sentryWebpackPluginOptions = {
  silent: true,
};

export default withSentryConfig(
  sentryWebpackPluginOptions
);

Steps to Reproduce
Following the installation instructions in the Sentry web UI, updated my sentry.server.config.js to the following:
import * as Sentry from '@sentry/nextjs';
import { ProfilingIntegration } from '@sentry/profiling-node';

Sentry.init({
  dsn: process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN
  tracesSampleRate: 1.0,
  profilesSampleRate: 1.0,
  integrations: [
    new ProfilingIntegration(),
  ],
});

Deploy to Vercel which runs npm build.
Potential follow-on issue from #164
Expected Result
The build should pass.
Actual Result
19:12:21.256 |  Failed to compile.
19:12:21.256 |
19:12:21.256 |<EMAIL_ADDRESS>19:12:21.256 | Module parse failed: Unexpected character '�' (1:0)
19:12:21.256 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:12:21.257 | (Source code omitted for this binary file)
19:12:21.257 |
19:12:21.257 | Import trace for requested module:
19:12:21.257 |<EMAIL_ADDRESS>19:12:21.257 |<EMAIL_ADDRESS>19:12:21.257 | ./sentry.server.config.js
19:12:21.257 | ./app/layout.tsx
19:12:21.257 |
19:12:21.257 |<EMAIL_ADDRESS>19:12:21.257 | Module parse failed: Unexpected character '�' (1:0)
19:12:21.257 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:12:21.257 | (Source code omitted for this binary file)
19:12:21.257 |
19:12:21.257 | Import trace for requested module:
19:12:21.257 |<EMAIL_ADDRESS>19:12:21.257 |<EMAIL_ADDRESS>19:12:21.257 | ./sentry.server.config.js
19:12:21.258 | ./app/layout.tsx
19:12:21.258 |
19:12:21.258 |<EMAIL_ADDRESS>19:12:21.258 | Module parse failed: Unexpected character '' (1:0)
19:12:21.258 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:12:21.259 | (Source code omitted for this binary file)
19:12:21.259 |
19:12:21.259 | Import trace for requested module:
19:12:21.259 |<EMAIL_ADDRESS>19:12:21.259 |<EMAIL_ADDRESS>19:12:21.259 | ./sentry.server.config.js
19:12:21.259 | ./app/layout.tsx
19:12:21.259 |
19:12:21.259 |<EMAIL_ADDRESS>19:12:21.259 | Module parse failed: Unexpected character '' (1:0)
19:12:21.259 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:12:21.259 | (Source code omitted for this binary file)
19:12:21.259 |
19:12:21.259 | Import trace for requested module:
19:12:21.260 |<EMAIL_ADDRESS>19:12:21.260 |<EMAIL_ADDRESS>19:12:21.260 | ./sentry.server.config.js
19:12:21.260 | ./app/layout.tsx
19:12:21.260 |
19:12:21.260 |<EMAIL_ADDRESS>19:12:21.260 | Module parse failed: Unexpected character '' (1:0)
19:12:21.260 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:12:21.260 | (Source code omitted for this binary file)
19:12:21.260 |
19:12:21.260 | Import trace for requested module:
19:12:21.260 |<EMAIL_ADDRESS>19:12:21.260 |<EMAIL_ADDRESS>19:12:21.260 | ./sentry.server.config.js
19:12:21.260 | ./app/layout.tsx
19:12:21.260 |
19:12:21.260 |
19:12:21.260 | > Build failed because of webpack errors

@haydenbleasel you need to define a loader for .node files. This seems like it uses webpack and not turbopack so https://webpack.js.org/loaders/node-loader/ should be the correct way to go. A quick search reveals this comment from nextjs team which explains how to set this up https://github.com/vercel/next.js/discussions/34040#discussioncomment-4904466

@JonasBa
I have completed the node-loader setup, but the following warning appears when building.
../../node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>Critical dependency: the request of a dependency is an expression

Import trace for requested module:
../../node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/layout.tsx

We're experiencing this problem as well.
yarnPath: .yarn/releases/yarn-3.6.0.cjs with .pnp.cjs
    "@sentry/core": "^7.57.0",
    "@sentry/nextjs": "^7.57.0",
    "@sentry/profiling-node": "^1.0.8",
    "@sentry/utils": "^7.57.0",
    "next": "13.4.4",

Here are our build logs when we try to use Next.js with App Router
- warn Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload
- wait compiling...
- error ./.yarn/unplugged/<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
./.yarn/unplugged/<EMAIL_ADDRESS>./.yarn/unplugged/@sentry-profiling-node-npm-1.0.8-6c9dd4d639/node_modules/@sentry/profiling-node/lib/ sync ^\.\/sentry_cpu_profiler\-.*\.node$
./.yarn/unplugged/<EMAIL_ADDRESS>./sentry.server.config.ts
./app/[orgSlug]/[thread]/page.tsx
- wait compiling /_error (client and server)...
- error ./.yarn/unplugged/<EMAIL_ADDRESS>- ```

I'm looking into this issue today, from what I can tell, the message you see at build time Critical dependency: the request of a dependency is an expression is only a warning and should not affect loading. That said, I have changed the module loading to no longer be async and removed the expression from require which I'm hoping will suppress this.

@doinki I will try to see if we can silence these warnings in the next version of the package.
@kachar, do you mind setting up the loader and seeing if you encounter the same issue?

same problem happening with the following packages
 "@prisma/client": "^4.15.0",
    "@sentry/nextjs": "^7.59.3",
    "@sentry/profiling-node": "^1.1.2",
    "next": "13.4.4",

@JonasBa mind providing an example with how this would work with vercel ncc? I cannot get this to work with webpack and nextjs as an external

This worked for me:
next.config.js:
/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    serverActions: true,
  },
  webpack: (config) => {
    config.externals = {
      "@sentry/profiling-node": "commonjs @sentry/profiling-node", // fixes https://github.com/getsentry/profiling-node/issues/170
    };
    return config;
  },
};

module.exports = nextConfig;

// Injected content via Sentry wizard below
// ...

@mmahalwy we have a section on bundlers in our readme, you can see how to configure it there https://github.com/getsentry/profiling-node#bundling
@Maxim-Mazurok what is the error that you see at build time?

npm run build

><EMAIL_ADDRESS>build
> next build

Failed to compile.

./node_modules/next/dist/compiled/next-server/pages.runtime.prod.js:1:32489
Module not found: Can't resolve 'critters'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/next/dist/server/future/route-modules/pages/module.compiled.js

> Build failed because of webpack errors
   Creating an optimized production build .

So I did npm i critters
And now I get this:
npm run build

><EMAIL_ADDRESS>build
> next build

 ⚠ Compiled with warnings

<EMAIL_ADDRESS>Critical dependency: the request of a dependency is an expression

Import trace for requested module:
<EMAIL_ADDRESS>./node_modules/next/dist/compiled/next-server/pages.runtime.prod.js
./node_modules/next/dist/server/future/route-modules/pages/module.compiled.js

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Box' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./ClickAwayListener' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./CssBaseline' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./darkScrollbar' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Fade' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Grow' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Hidden' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./MenuList' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./NoSsr' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Popper' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Portal' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./RadioGroup' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Slide' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Stack' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./SwipeableDrawer' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./TextareaAutosize' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./useMediaQuery' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./usePagination' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./useScrollTrigger' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./Zoom' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./GlobalStyles' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=useTheme&wildcard!=!./generateUtilityClass' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/compareTable.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Box' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./ClickAwayListener' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./CssBaseline' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./darkScrollbar' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Fade' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Grow' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Hidden' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./MenuList' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./NoSsr' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Popper' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Portal' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./RadioGroup' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Slide' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Stack' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./SwipeableDrawer' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./TextareaAutosize' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./useMediaQuery' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./usePagination' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./useScrollTrigger' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./Zoom' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./GlobalStyles' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

<EMAIL_ADDRESS>The requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./generateUtilityClass' contains conflicting star exports for the name '__esModule' with the previous requested module '__barrel_optimize__?names=autocompleteClasses,styled,useTheme&wildcard!=!./utils'

Import trace for requested module:
<EMAIL_ADDRESS>./app/utils/virtualizedInput.tsx
./app/compareForm.tsx
./app/home.tsx
./app/page.tsx

./node_modules/retry-request/index.js
Module not found: Can't resolve 'request' in '/home/maxim/my-project/node_modules/retry-request'

Import trace for requested module:
./node_modules/retry-request/index.js
./node_modules/google-gax/build/src/streamingCalls/streaming.js
./node_modules/google-gax/build/src/index.js
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>./app/api/compare/route.ts

 ✓ Linting and checking validity of types
 ✓ Collecting page data
   Generating static pages (1/6) [=   ]
TypeError: Cannot read properties of null (reading 'useContext')
    at ei.useContext (/home/maxim/my-project/.next/server/chunks/871.js:49:188589)
    at eb (/home/maxim/my-project/.next/server/chunks/871.js:36:24272)
    at eE (/home/maxim/my-project/.next/server/chunks/871.js:36:14841)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141914)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at aa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141462)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:142065)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:144318)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at ca (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:158062)
TypeError: Cannot read properties of null (reading 'useContext')
    at t.useContext (/home/maxim/my-project/.next/server/chunks/992.js:9:5495)
    at m (/home/maxim/my-project/.next/server/chunks/172.js:1:4501)
    at Wc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)
TypeError: Cannot read properties of null (reading 'useContext')
    at t.useContext (/home/maxim/my-project/.next/server/chunks/992.js:9:5495)
    at m (/home/maxim/my-project/.next/server/chunks/172.js:1:4501)
    at Wc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)

Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useContext')
    at t.useContext (/home/maxim/my-project/.next/server/chunks/992.js:9:5495)
    at m (/home/maxim/my-project/.next/server/chunks/172.js:1:4501)
    at Wc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)

Error occurred prerendering page "/500". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useContext')
    at t.useContext (/home/maxim/my-project/.next/server/chunks/992.js:9:5495)
    at m (/home/maxim/my-project/.next/server/chunks/172.js:1:4501)
    at Wc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at $c (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at Zc (/home/maxim/my-project/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:145)
TypeError: Cannot read properties of null (reading 'useContext')
    at ei.useContext (/home/maxim/my-project/.next/server/chunks/871.js:49:188589)
    at eb (/home/maxim/my-project/.next/server/chunks/871.js:36:24272)
    at eE (/home/maxim/my-project/.next/server/chunks/871.js:36:14841)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141914)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at aa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141462)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:142065)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:144318)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156228)

Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useContext')
    at ei.useContext (/home/maxim/my-project/.next/server/chunks/871.js:49:188589)
    at eb (/home/maxim/my-project/.next/server/chunks/871.js:36:24272)
    at eE (/home/maxim/my-project/.next/server/chunks/871.js:36:14841)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141914)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at aa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141462)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:142065)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:144318)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.pro
   Generating static pages (5/6) [==  ]
   Creating an optimized production build ...TypeError: Cannot read properties of null (reading 'useContext')
    at ei.useContext (/home/maxim/my-project/.next/server/chunks/871.js:49:188589)
    at eb (/home/maxim/my-project/.next/server/chunks/871.js:36:24272)
    at eE (/home/maxim/my-project/.next/server/chunks/871.js:36:14841)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141914)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at aa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141462)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:142065)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:144318)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at ca (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.pro
   Generating static pages (5/6) [=== ]
TypeError: Cannot read properties of null (reading 'useContext')
    at ei.useContext (/home/maxim/my-project/.next/server/chunks/871.js:49:188589)
    at eb (/home/maxim/my-project/.next/server/chunks/871.js:36:24272)
    at eE (/home/maxim/my-project/.next/server/chunks/871.js:36:14841)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141914)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at aa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141462)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:142065)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:144318)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156228)

Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useContext')
    at ei.useContext (/home/maxim/my-project/.next/server/chunks/871.js:49:188589)
    at eb (/home/maxim/my-project/.next/server/chunks/871.js:36:24272)
    at eE (/home/maxim/my-project/.next/server/chunks/871.js:36:14841)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141914)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at aa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:141462)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:142065)
    at sa (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:144318)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.prod.js:1:156001)
    at ia (/home/maxim/my-project/node_modules/next/dist/compiled/next-server/app-page-experimental.runtime.pro
 ✓ Generating static pages (6/6)

> Export encountered errors on following paths:
        /_error: /404
        /_error: /500
        /_not-found
        /page: /
   Creating an optimized production build .

I've tried using latest stable next, and here's the next config:
/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    serverActions: true,
  },
  webpack: (config) => {
    config.externals = {
      "@sentry/profiling-node": "commonjs @sentry/profiling-node", // fixes https://github.com/getsentry/profiling-node/issues/170
    };
    return config;
  },
};

module.exports = nextConfig;

// Injected content via Sentry wizard below

const { withSentryConfig } = require("@sentry/nextjs");

module.exports = withSentryConfig(
  module.exports,
  {
    // For all available options, see:
    // https://github.com/getsentry/sentry-webpack-plugin#options

    // Suppresses source map uploading logs during build
    silent: true,
    org: "travel-times",
    project: "javascript-nextjs",
  },
  {
    // For all available options, see:
    // https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/

    // Upload a larger set of source maps for prettier stack traces (increases build time)
    widenClientFileUpload: true,

    // Transpiles SDK to be compatible with IE11 (increases bundle size)
    transpileClientSDK: true,

    // Routes browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers (increases server load)
    tunnelRoute: "/monitoring",

    // Hides source maps from generated client bundles
    hideSourceMaps: true,

    // Automatically tree-shake Sentry logger statements to reduce bundle size
    disableLogger: true,
  }
);

my next setup is pretty vanilla, using app router.
sentry configs also pretty much as wizard created them:
// This file configures the initialization of Sentry on the client.
// The config you add here will be used whenever a users loads a page in their browser.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
  environment: process.env.NEXT_PUBLIC_ENVIRONMENT_NAME,

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false, // need to change `disableLogger` in next config to make this work

  replaysOnErrorSampleRate: 1.0,

  // This sets the sample rate to be 10%. You may want this to be 100% while
  // in development and sample at a lower rate in production
  replaysSessionSampleRate: 0.1,

  // You can remove this option if you're not planning to use the Sentry Session Replay feature:
  integrations: [
    new Sentry.Replay({
      // Additional Replay configuration goes in here, for example:
      // maskAllText: true,
      // blockAllMedia: true,
    }),
  ],
});

etc, hope it helps.
I decided to defer node profiling, it's not very important for me at this stage of the project.

@Maxim-Mazurok, that is very weird. We do not use the critters package so it's unclear to me why this happens.
The error I'm seeing seems like a nextj react prerender error unrelated to @sentry/profiling-node
Creating an optimized production build ...TypeError: Cannot read properties of null (reading 'useContext')
    at ei.useContext (/home/maxim/my-project/.next/server/chunks/871.js:49:188589)

I'm going to try and setup a nextjs app and see if I can reproduce

I also use MUI components and most of my components are "use client"; if that makes a difference... Overall I feel like nextjs is doing so much magic under the hood that the errors I'm getting on the way make very little sense, maybe it's just because it's my first nextjs project.

Related to critters: https://github.com/vercel/next.js/issues/34763

Hi I wanted to reopen this thread.
I'm trying to setup profiling for my next.js application. I modified sentry.server.config.ts with the following

profilesSampleRate: 1.0,
integrations: [
newProfilingIntegration(),
]

and have the following sentry versions defined:
"@sentry/integrations": "^7.74.1",
"@sentry/nextjs": "^7.74.1",
"@sentry/profiling-node": "^1.2.1",
"@sentry/types": "^7.74.1",

. This causes my build to fail with the following error:
./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./sentry.server.config.ts
./app/page.tsx

./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./sentry.server.config.ts
./app/page.tsx

./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./sentry.server.config.ts
./app/page.tsx

./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./sentry.server.config.ts
./app/page.tsx

./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./node_modules/.pnpm/@sentry+profiling-node<EMAIL_ADDRESS>./sentry.server.config.ts
./app/page.tsx

I saw this related thread and added the following line to my next.config.js file:
config.externals = {
'@sentry/profiling-node':'commonjs @sentry/profiling-node',
}

and then installed critters but then received the following error:

SyntaxError: Unexpected identifier
--
14:05:12.695 | at internalCompileFunction (node:internal/vm:73:18)
14:05:12.695 | at wrapSafe (node:internal/modules/cjs/loader:1178:20)
14:05:12.695 | at Module._compile (node:internal/modules/cjs/loader:1220:27)
14:05:12.695 | at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
14:05:12.695 | at Module.load (node:internal/modules/cjs/loader:1119:32)
14:05:12.695 | at Module._load (node:internal/modules/cjs/loader:960:12)
14:05:12.695 | at Module.require (node:internal/modules/cjs/loader:1143:19)
14:05:12.695 | at mod.require (/vercel/path0/node_modules/.pnpm/next@13.5.3_@babel+core@7.23.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/require-hook.js:64:28)
14:05:12.695 | at require (node:internal/modules/cjs/helpers:121:18)
14:05:12.695 | at t.f.require (/vercel/path0/.next/server/webpack-runtime.js:1:1515) {
14:05:12.695 | type: 'SyntaxError'```

which wasn't very illustrative. I was wondering if there were any ideas on how to handle this.

@nhewage1997 I have the same problem. Haven't you fixed it yet?
Versions:
"next": "^13.5.4",
"@sentry/nextjs": "^7.77.0",
"@sentry/profiling-node": "^1.2.6",

@nhewage1997 I have the same problem. Haven't you fixed it yet?
Versions:
"next": "^13.5.4",
"@sentry/nextjs": "^7.77.0",
"@sentry/profiling-node": "^1.2.6",

@nhewage1997 you shouldn't need to install critters for this to work. Do you mind uninstalling it and telling me if it still fails?
@tua-Mascot can you please share a relevant stack trace and confirm that you marked @sentry/profiling-node as an external module?

I have the same issue when trying to integrate profiling in a nestjs project in mono-repo mode. Adding the package as external does not work. I removed profiling for now until the issue is fixed.

@JonasBa Sure
Stack trace
Failed to compile.

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/not-found.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/not-found.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/not-found.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/not-found.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/not-found.tsx

> Build failed because of webpack errors

and I added this to next.config.js
experimental: {
    serverComponentsExternalPackages: ['@sentry/profiling-node']
  },

@JonasBa Sorry to bother you, but more than a week has passed. Are there any updates/news?

@tua-Mascot mind creating a reproducible case for this? I think that adding your component to external packages didn't work as the build system is still trying to resolve that file

I have the same issue, when marking it as external I'm missing the "critters" package.

Adding serverComponentsExternalPackages: ['@sentry/profiling-node'], seems to fix the issue for Next.js 14. Which document do you import/require @sentry/profiling-node package? It should be inside sentry.server.{js,ts}

Getting this error as well on a new project with Sentry setup.
I've tried doing ...
serverComponentsExternalPackages: ['@sentry/profiling-node']
in the next config, but hasn't changed anything.
Key relevant packages
"next": "^14.0.4",
"@sentry/nextjs": "^7.88.0",
"@sentry/profiling-node": "^1.3.2",

Happy to try and provide more info if that will help, otherwise disabling profiling for the time being

I got the same error after I imported the Hero component to the page and it contained a video
NOTE: the component works well on storybook
./public/assets/videos/hero.mp4
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Is there any update? Meet the same issue.ServerComponentsExternalPackages only works for development, still get error when building.

@nikolovlazar This is something I just ran into. Which is the issue I mentioned during the webinar just now.
I also don't know why it's trying to read the darwin file instead of linux to be honest. Maybe thats the issue?
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Mon Nov 6 23:32:38 UTC 2023
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: 8.14.1

@JesseKoldewijn Your Next.js config file does not have experimental.serverComponentsExternalPackages attribute. Ref: https://github.com/getsentry/profiling-node#bundling

@JesseKoldewijn Your Next.js config file does not have experimental.serverComponentsExternalPackages attribute. Ref: https://github.com/getsentry/profiling-node#bundling

Ah check. Thanks, will check if that's the fix later today👌

@anonrig the external package config fixed the issue for me indeed. Must have either missed this in the docs within the sentry UI or it wasn't mentioned in there at all. If this fix could globally fix this for more sentry+next users I could open another PR on Next to auto include this package in the exclude list (done this before with a couple of packages)

@anonrig the external package config fixed the issue for me indeed. Must have either missed this in the docs within the sentry UI or it wasn't mentioned in there at all. If this fix could globally fix this for more sentry+next users I could open another PR on Next to auto include this package in the exclude list (done this before with a couple of packages)

That would be a good idea. Thanks!

@JesseKoldewijn that would be a very good idea, thank you for proposing that. P.S: I'm happy to open the PR, I didn't think NextJS would allow something like that and was under the impression they'd want developers to manage this on their own

Im opening an issue on Next.js's side already and added package to this list in the 13.x releases as well. so I prob got the PR up in a couple of minutes 👍

Issue created: https://github.com/vercel/next.js/issues/60853

PR is open, lets see when it will be merged. Also noticed that this wasn't the first sentry package in there funny enough 😉

Just woke up and saw that the fix was merged into the canary branch of Next.js🤙

Incase anybody wants to bypass setting the experimental config entry in Next.js already and is fine with using the canary channel of Next.js you can already use the fix I pushed through the PR by upgrading to Next.js release v14.1.1-canary.1

Is there any update? Meet the same issue.ServerComponentsExternalPackages only works for development, still get error when building.

I've personally tested using the integration with external package enabled which worked perfectly. Could you possibly check if the issue on your end persists if you upgrade Next.js to the latest canary release?
ps. this can be done by targeting the following install directive next@canary

Part of what is frustrating with this issue is that many folks run this through nextjs or similar which largely abstract build configurations while building and executing your code for different environments (example is server vs edge) and depending on their versions, they might even use different underlying build tools. The result of this is that many folks are not aware of how their code is built (rightfully so as tools should just work) or how their code is executed at runtime, leaving library maintainers largely in a bit of a tough spot to debug.
When you see an error like Module parse failed: Unexpected character '�' (1:0), it means your build tooling is not configured to recognize the file as binary and attempts to read it as utf8. Since it fails to make sense of the binary data as utf8, it will display the unicode replacement character � and correctly errors.
Marking packages as external fixes this as it instructs the bundler to skip such files and instead require them at runtime, and while this does work, it leaves you without the realizing the gains that bundles code has on your script cold start performance (something highly relevant to something like profiling where we want to keep the runtime impact minimal)
In other words, by requiring packages marked as external, the module loader needs to perform additional disk i/o to be able to evaluate the module and execute it, which impacts cold start performance. AWS has a good article on optimizing cold start performance in serverless that I recommend reading.
All this to say that when you do encounter issues like this, you should check with your platform provider or your bundler configuration if it is possible to bundle packages containing binary files as it will both make your code faster to run as well as save you some infra costs.

I forgot to add that in order to mitigate the impact on your cold start performance when @sentry/profiling-node is marked as external, we publish the library as a single index.js executable where all of its dependencies are bundled. This way, even if you mark the library as external, the module loader is only executed once for the @sentry/profiling-node module js file and once to load the binary file.

@JonasBa
Unfortunately, in my case the problem is still reproducible.
I checked on two versions of next.js - 14.1.0 and 14.1.1-canary.4
I made a fresh repository with next.config.js and sentry configs are close to the settings in my project.
If we add "use client" to the very top of the page.tsx file, then we get (probably) the same error
Failed to compile.

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./app/page.tsx

But if you delete the "use client", then everything works.
Link to the repository - https://github.com/tua-Mascot/sentry-profiling-node-test

@JonasBa Unfortunately, in my case the problem is still reproducible. I checked on two versions of next.js - 14.1.0 and 14.1.1-canary.4
I made a fresh repository with next.config.js and sentry configs are close to the settings in my project. If we add "use client" to the very top of the page.tsx file, then we get (probably) the same error
Failed to compile.

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./app/page.tsx

But if you delete the "use client", then everything works.
Link to the repository - https://github.com/tua-Mascot/sentry-profiling-node-test

In that case it crashes because the "use client" flag indicates that the component also has to run in de browser. Due to this flag the component wont be using the external package config or the Next.js internal packages list.
Its kinda the same problem as when you try to run native node.js modules in the browser.

@JesseKoldewijn
Thank you for the clarification. But I didn't fully understand. Does this mean that I can't use "use client" if I want to use @sentry/profiling-node?

@JesseKoldewijn

Thank you for the clarification. But I didn't fully understand. Does this mean that I can't use "use client" if I want to use @sentry/profiling-node?

If you only use the node-profiler within a server action, you can. Otherwise, you can't. Since a client component runs as mentioned before both on the server and client👍

Is there a going to be a fix in the future for support for the 'use client' directive for the nextjs app router in the future for profiling?

The node profiler is not intended to run on the client since the browser doesn't run node. So as long as you exclude it from running on the client it might run fine in client components.

@JesseKoldewijn Your Next.js config file does not have experimental.serverComponentsExternalPackages attribute. Ref: https://github.com/getsentry/profiling-node#bundling

Ah check. Thanks, will check if that's the fix later today👌

Unfortunately, not work for me. Here is the verison I used
"@sentry/nextjs": "7.92.0",
"@sentry/profiling-node": "^1.3.5",
"next": "^14.1.1-canary.25",
`
// sentry.server.config
import * as Sentry from "@sentry/nextjs";
import { ProfilingIntegration } from '@sentry/profiling-node';
Sentry.init({
dsn: process.env.NODE_ENV === "production"<EMAIL_ADDRESS>: "",
// Set tracesSampleRate to 1.0 to capture 100%
// of transactions for performance monitoring.
// We recommend adjusting this value in production
tracesSampleRate: 1.0,
profilesSampleRate: 1.0,
integrations: [
// todo fix issue https://github.com/getsentry/profiling-node/issues/170
new ProfilingIntegration(),
],
// ...
// Note: if you want to override the automatic release value, do not set a
// release value here - use the environment variable SENTRY_RELEASE, so
// that it will also get attached to your source maps
});
`

@JesseKoldewijn Your Next.js config file does not have experimental.serverComponentsExternalPackages attribute. Ref: https://github.com/getsentry/profiling-node#bundling

Ah check. Thanks, will check if that's the fix later today👌

@JesseKoldewijn Unfortunately, not work for me. Here is the verison I used
"@sentry/nextjs": "7.92.0",
"@sentry/profiling-node": "^1.3.5",
"next": "^14.1.1-canary.25",

Are you using the node profiler in a client component by chance?

@JesseKoldewijn Your Next.js config file does not have experimental.serverComponentsExternalPackages attribute. Ref: https://github.com/getsentry/profiling-node#bundling

Ah check. Thanks, will check if that's the fix later today👌

@JesseKoldewijn Unfortunately, not work for me. Here is the verison I used
"@sentry/nextjs": "7.92.0",
"@sentry/profiling-node": "^1.3.5",
"next": "^14.1.1-canary.25",

Are you using the node profiler in a client component by chance?

@JesseKoldewijn No, I use the default setting in my sentry.server.config file only. As the code below

And I found there are confilts during install, because sentry/profiling need a peerDependence for nextjs highest 14.0.

So maybe sentry do not fully support next14 right now.

Just to add to this, I also have the same issue. I tried fixing it by following the various recommendations you gave :

Upgrade Next from 13.4.9 to 14.1.0
Upgrade Node to 18.17.0 (Next 14 requirement)
Added the following snippet to next.config.js{
  experimental: {
    serverComponentsExternalPackages: [
      '@sentry/profiling-node',
    ],
  },
}```

I still get the same errors as before :

Failed to compile.

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/(auth)/layout.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/(auth)/layout.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/(auth)/layout.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/(auth)/layout.tsx

<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
<EMAIL_ADDRESS><EMAIL_ADDRESS>./sentry.server.config.ts
./src/app/(auth)/layout.tsx

> Build failed because of webpack errors

I also use MUI components, so I got 'use client'; basically everywhere.

@JesseKoldewijn Your Next.js config file does not have experimental.serverComponentsExternalPackages attribute. Ref: https://github.com/getsentry/profiling-node#bundling

Ah check. Thanks, will check if that's the fix later today👌

@JesseKoldewijn Unfortunately, not work for me. Here is the verison I used
"@sentry/nextjs": "7.92.0",
"@sentry/profiling-node": "^1.3.5",
"next": "^14.1.1-canary.25",

Are you using the node profiler in a client component by chance?

@JesseKoldewijn No, I use the default setting in my sentry.server.config file only. As the code below
And I found there are confilts during install, because @sentry/next need a peerDependence for nextjs highest 14.0.  So maybe sentry do not fully support next14.1 right now.

As mentioned before, the package does work in Next.js 14.1.1-canary.1 and later. But without a reproduction repo and only the server config file I can't really make an educated guess on why it doesn't work in your project.

To anybody with this issue past next release 14.1.1-canary.1 please check out my repo below which is a working example of the fix within nextjs I've implemented.
github.com/JesseKoldewijn/Jereko

I had similar issues but running Node 18, Express.js, and Webpack. I was able to get passed the Unexpected character '�' (1:0) issue by adding @sentry/profiling-node': 'commonjs @sentry/profiling-node to externals.
...
module.exports = {
  entry: './src/index.ts',
  externals: {
    '@sentry/profiling-node': 'commonjs @sentry/profiling-node',
  },
  devtool: 'inline-source-map',
  target: 'node',
  module: {
    rules: [
...

But now I'm experiencing a new error message that I have not figure out how to resolve during webpack build. Does any have any suggestions?
...
webpack://eh-replicache-api/node_modules/@sentry/profiling-node/lib/index.js:652
const DEBUG_BUILD$1 = __DEBUG_BUILD__;
^

ReferenceError: __DEBUG_BUILD__ is not defined
    at<EMAIL_ADDRESS>(webpack://eh-replicache-api/node_modules/@sentry/profiling-node/lib/index.js:652:1)
    at __webpack_require__ (webpack://eh-replicache-api/webpack/bootstrap:19:1)
    at Object../src/utils/sentry/initSentry.ts (webpack://eh-replicache-api/src/utils/sentry/initSentry.ts:2:1)
    at __webpack_require__ (webpack://eh-replicache-api/webpack/bootstrap:19:1)
    at Object../src/index.ts (webpack://eh-replicache-api/src/index.ts:16:1)
    at __webpack_require__ (webpack://eh-replicache-api/webpack/bootstrap:19:1)
    at <anonymous> (webpack://eh-replicache-api/webpack/startup:4:1)
    at Object.<anonymous> (webpack://eh-replicache-api/webpack/startup:4:1)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)

I've ran into a similar issue.
Tried to add
{
  experimental: {
    serverComponentsExternalPackages: [
      '@sentry/profiling-node',
    ],
  },
}

Which works as long as I don't have a use client component.
I'm in
"next": "^14.1.3",
"@sentry/browser": "^7.106.1",
"@sentry/nextjs": "^7.106.0",
"@sentry/node": "^7.106.1",
"@sentry/profiling-node": "^7.106.1",

Wondering if there is a way to only enable the Profiling in the pages router and disable it in the app router?

I've ran into a similar issue.
Tried to add
{
  experimental: {
    serverComponentsExternalPackages: [
      '@sentry/profiling-node',
    ],
  },
}

Which works as long as I don't have a use client component. I'm in
"next": "^14.1.3",
"@sentry/browser": "^7.106.1",
"@sentry/nextjs": "^7.106.0",
"@sentry/node": "^7.106.1",
"@sentry/profiling-node": "^7.106.1",

Wondering if there is a way to only enable the Profiling in the pages router and disable it in the app router?

Are you importing the @sentry/profiling-node package inside a component which is marked with "use client"? Because this will not work due to the component also runs in the browser.

I've ran into a similar issue.
Tried to add
{
  experimental: {
    serverComponentsExternalPackages: [
      '@sentry/profiling-node',
    ],
  },
}

Which works as long as I don't have a use client component. I'm in
"next": "^14.1.3",
"@sentry/browser": "^7.106.1",
"@sentry/nextjs": "^7.106.0",
"@sentry/node": "^7.106.1",
"@sentry/profiling-node": "^7.106.1",

Wondering if there is a way to only enable the Profiling in the pages router and disable it in the app router?

Are you importing the @sentry/profiling-node package inside a component which is marked with "use client"? Because this will not work due to the component also runs in the browser.

Thank you @JesseKoldewijn . Sorry for my late response as well.
We don't import @sentry/profiling-node package in any specific component. This is how we configured Sentry Profiling. We only has the import in the config files. I guess this enables the profiling for all components?
// sentry.server.config.ts
import * as Sentry from '@sentry/nextjs';
import { ProfilingIntegration } from '@sentry/profiling-node';
Sentry.init({
	profilesSampleRate: 1,
	integrations: [new ProfilingIntegration()],
});

// sentry.client.config.ts
import * as Sentry from '@sentry/nextjs';
Sentry.init({
	profilesSampleRate: 1,
	integrations: [
		new Sentry.BrowserProfilingIntegration(),
	],
});

// next.config.mjs
import { withSentryConfig } from '@sentry/nextjs';
export default withSentryConfig({
	headers: async () => {
		return [
			{
				source: "/(.*)",
				headers: [
					{
						key: "Document-Policy",
						value: "js-profiling"
					}
				]
			}
		]
	},
});


AzDOS extension install ssis devops tools

@WendyYes : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@WendyYes : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add siac renter commands for listing upload and download queues

siac renter uploads lists only files that are currently uploading.
siac renter downloads [--history/-H] lists only files that are currently downloading. The --history flag shows previously downloaded files in addition to the currently downloading files. There is no --history flag for siac renter uploads because the backend does not yet support this.
I also moved all command.AddCommand(subCommand) into init() functions in the respective command's file. This way the main function doesn't need to worry about adding all of the subcommands.

hmm. Not sure how I feel about all those inits. I kind of like keeping the whole structure (and all the flags) in main.go.

My reasoning for using inits is because it's nice to have the flag variables in the same file as the functions that use them, and the flags in the same file as the the flag variables. But there's a benefit to having all of the flags and commands in one place too. I'll revert that commit.

Should be all good now.


c3 rounding values with negative values

Revising some "old" stackoverflow  questions on rpivotTable I found an odd one here .
As it is possible to see from the example on SO, c3 bar chart rounds the negative numbers, and only those.
I just tested it with pivottable 2.11.0 and the behaviour is still there. Is this intended for some reason?
Please note it is a minor issue.  :)

Unfortunately this is a C3 bug :(

Update: this is not a C3 bug

Sorry, hit close too early! meant to add "... and will be fixed shortly!"

This is now fixed, and I recommend that rpivotTable be updated ASAP with the new code... sorry for the bug!


[revive] allow unused variables starting with underscore

What does this PR do?

Allow using variables starting with underscore without revive complaining it's unused.
Motivation

_ is not explicit on what the variable is, and it can be useful to make it clear even when the variable is unused.
In that case, allowing using _somename is useful.
Additional Notes

Feature added in https://github.com/mgechev/revive/pull/858.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

I tested manually that it worked as expected.

/merge


Invalid Mesh

Hello,
I run this example app without a license key. After every scan I get the error message "Invalid Mesh". What I do wrong or do I need a license key ?

You'll need a license key to get a valid and complete mesh. Please see the README.md file in the code directory and the "Documentation" folder in the Structure SDK download for guidance.

The link from the documentation to get the license key doesn't work. What is the correct link ? Is the license key include if I had by a sensor or is that a extra payment?

-- Please reply above this line --
Hello Structureio/sample-Scanner,
We received your email request!
Someone from our team will get back to you as soon as possible.
Happy Scanning,
The Structure Team Bot
STRUCTURE 2023 HOLIDAY CALENDAR (We will be closed on these dates.)
* Veterans Day(Fri, Nov 10)
* Thanksgiving _(Thu, Nov 23)_
* Thanksgiving _(Fri, Nov 24)_
* Christmas Eve _(Fri, Dec 22)_
* Christmas Day _(Mon, Dec 25)_
* New Years Eve _(Fri, Dec 29)_

You should be able to create an account here: https://console.cloud.structure.io/login
After setting up your account, a team member will contact you to assist in getting up and running. The standard license includes the Structure Sensor scan export feature. In order to export the mesh, all apps require a license key.
Additional paid features, such as Apple TrueDepth and Apple LiDAR support, are available. If you are interested in testing those out just let us know. We do offer educational and small business terms.


Supported liquid filters

Hi, Is it possible to have in the doc the list of all supported liquid filters?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e02fc497-8e32-b0e1-6ae3-cf1039cc1c7b
Version Independent ID: 2ce45d89-18b7-8465-8ab7-bef9b544a474
Content: Convert JSON data with Liquid transforms - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-enterprise-integration-liquid-transform.md
Service: logic-apps
GitHub Login: @divyaswarnkar
Microsoft Alias: LADocs; divswa

@middlewaysas Thanks for the feedback! We are currently investigating and will update you shortly.

Hi, In the beginning of document we have provided link to Liquid documentation where you can find the list of filters. Since we don't own the filter list, we do not intend to put that list in this document.

Hi,
Ok but a few months ago when I tested the "Sort" filter, it was not supported by the liquid maps in Logic Apps. It means for me that you are not currently supporting all the filters. Can you please confirm?

sort should work fine. Please share your map. You can email me at<EMAIL_ADDRESS>

@divyaswarnkar Hi Divya, has this issue been resolved?

@divyaswarnkar Thanks, Divya! Although I don't think this is a doc issue anymore, so we should close this issue, but we could move the link for the filters higher in the topic, which I can do.
@middlewaysas If you want to reopen this issue, please post on the Logic Apps MSDN forum. Thanks!
@mike-urnun-msft Mike, #please-close, thanks!

@middlewaysas \We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

@middlewaysas We've published an update that clarifies that the filters list exists elsewhere:
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-enterprise-integration-liquid-transform#create-liquid-template-or-map-for-your-integration-account

Hi I am trying to divide two numbers using Liquid map in logic app. but it's not working. here my simple mapping code ,
{
"unitWeight":"{{ 4 | Divided_by: 2 }}"
}

Hi, Please try "DividedBy" and it should work. We are also going to update the doc with all the filter names.

@divyaswarnkar, the plus filter is not working as expected. Please suggest.
mapping code,
{
"index":{{ 1 | plus: 5 }},
}
Result:
{
"index":1,
}

Can you try with upper case P  i.e use Plus

Can you try with upper case P i.e use Plus

Thanks, it worked

@divyaswarnkar, Could you please suggest the syntax for dividedBy. This is not working as expected using Liquid map in logic app.
mapping code:
{%- assign test = 10 | divided_by: 2 -%}
{{test}}
Result: 10 (instead of 5)

Hi @kpvnreddy,
Did you try Divya's suggestion to use "DividedBy" as the filter names are case sensitive?

Hi. I have some problems with the Uniq filter when running transformation in Logic App. When I uses different online tools the mapping is correct but not in LA.
{% assign transactions = content.Table1 | Map: 'faktnr' | Uniq %}
and content.Table1 contains 3 records with faktnr 44084, 44084, 44089. In online tool when I try {{transactions | size}} I get 2 as result, but in my Logic App {{transactions | Size}} = 3
Any suggestions?

Please share the map and input and we will take a look

Here is the map:
{% assign transactions = content.Table1 | Map: "faktnr" | Uniq %}{
"saveBundleList": {
"bundlelist": {
"allowDifference": false,
"bundles": [
{
"bundleDirectAccounting": false,
"name": "sample",
"sort": 0,
"yearId": "2019",
"vouchers": [{% for voucher in transactions %}
{
"transactionNo": "1337"
}{% if forloop.last == false %},{% endif %}{% endfor %}
]
}
],
"defaultCustomerId": 0,
"directLedger": false,
"saveOption": "1"
}
}
}

And input:
{
"content": {
"Table1": [
{
"bundleId": "2019-10-21 15:35:38.420",
"faktnr": 44084,
"ktonr": "2400",
"momskod": null,
"debbel": 0,
"krebel": 37000,
"faktffdat": "2019-10-28T00:00:00",
"faktdat": "2019-10-18T00:00:00",
"kundbetalarenr": "801028",
"Attachement": "Test"
},
{
"bundleId": "2019-10-21 15:35:38.420",
"faktnr": 44084,
"ktonr": "1460",
"momskod": 1,
"debbel": 37000,
"krebel": 0,
"faktffdat": "2019-10-28T00:00:00",
"faktdat": "2019-10-18T00:00:00",
"kundbetalarenr": "801028",
"Attachement": "Test"
},
{
"bundleId": "2019-10-18 11:17:01.110",
"faktnr": 44089,
"ktonr": "2400",
"momskod": null,
"debbel": 0,
"krebel": 170,
"faktffdat": "2019-10-28T00:00:00",
"faktdat": "2019-10-18T00:00:00",
"kundbetalarenr": "801028",
"Attachement": "Test"
}
]
}
}

The problem is that I only want two "vouchers" one for each unique "faktnr". One for faktnr = 44084 and one for faktnr = 44089

This is the output when I run it in a Logic App:
{
"saveBundleList": {
"bundlelist": {
"allowDifference": false,
"bundles": [
{
"bundleDirectAccounting": false,
"name": "sample",
"sort": 0,
"yearId": "2019",
"vouchers": [
{
"transactionNo": "1337"
},
{
"transactionNo": "1337"
},
{
"transactionNo": "1337"
}
]
}
],
"defaultCustomerId": 0,
"directLedger": false,
"saveOption": "1"
}
}
}


Add an option for active job count

Commands like distributedLoad and distributedCp submits jobs to the cluster job service. The command creates 1 job for each file. By default the command allows up to 3000 jobs to be submitted and waiting for completion. When there are many distributedLoad/Cp commands running by many users, there may be too many jobs in the queue for the job service.
This change intends to add a way to throttle the job submission speed at the command side. Especially when the distributedLoad/Cp jobs are submitted with automated scripts, we may want less than 3000 jobs to run with each command. Maybe find a balance between speed and resource claim, like 1000 or 500.
Volume control on Alluxio job service is beyond the scope of this PR.
Example:
$ bin/alluxio fs distributedLoad --job-count 1000 /
Allow 1000 active jobs
...

Codecov Report

Merging #12795 (2b3f27f) into master (3a5d11a) will decrease coverage by 23.07%.
The diff coverage is 0.00%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 855e85d...2b3f27f. Read the comment docs.

how does this interact with the alluxio.job.worker.threadpool.size property? does the latter not control the former somehow as well? because ultimately if there is no jobworker threads, we can't run the distributed load jobs?

Closed since resource is already managed by alluxio.job.worker.threadpool.size

@yuzhu Actually on 2nd thought, I think it's reasonable to have the control on the submitter side anyways.

this doesn't really do what you think it does. And when users reduce this down to a number like 100, it's going to be really slow because those jobs are going to be really slow even when there is only one job worker that handles at most 20 concurrent jobs because this setting is not really about concurrent jobs.
This is a very misleading setting.

@bradyoo I don't understand why this flag is not what what we think it means? I think it does do what we think, but if tasks are very short compared to the heartbeat time, there will be a lot of unused job worker resources, right?

@bradyoo @gpang I believe a better name would be "active jobs" rather than "concurrent jobs", because the concurrency is provided by the job worker and the corresponding job worker threadpool.
Yea 20 is going to be unreasonably small. But there might be some good numbers like 500 or 1000 that finds a balance between speed and being nice to the other users, right?

LGTM

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.4 please

alluxio-bot, cherry-pick this to branch-2.4 please

alluxio-bot, cherry-pick this to branch-2.4 please


Remove parity_wasm dependency from wasmi_core

Codecov Report

Merging #390 (679ba18) into master (2236434) will not change coverage.
The diff coverage is 91.66%.

:exclamation: Current head 679ba18 differs from pull request most recent head ce59f29.  Take ten seconds to tell us how you rate us.


Since version 1.8.3-0.1.dev.gitaa6c8c2.fc33 all console utilities in container working only in 80x25 chars .

Since version 1.8.3-0.1.dev.gitaa6c8c2.fc33 all console utilities in container working only in 80x25 chars .

Last good version is 1.8.2-0.9.dev.gitcccd05c.fc33

@mheon @haircommander @giuseppe Terminal resize broke?

More details would be greatly appreciated - is this with podman exec, or podman run, or both?

More details would be greatly appreciated - is this with podman exec, or podman run, or both?

It's the result of both commands.

$ podman run my-super-container
$ podman exec -it inside mc

#5613 to fix


refactor: Search Tile & Component

[x] Fetch the updatedAt field from backend.
[x] Show updated At date and time for a particular package in Search.
[x] refactor Search, Pagination & Navbar component and reduce nesting.
[x] refactor & reduce string comparisons.

Thanks @arteevraina


Include name property in onChange(selected)

This would make it easier to use a single onChange handler for tracking current state.
e.g. The same change handler
const onChange = (selected) => {
  this.setState({ [selected.name]: selected.value })
}

Could be used for
<Select
    name="form-field-name-one"
    value="one"
    options={optionsForOne}
    onChange={onChange}
  />

<Select
    name="form-field-name-two"
    value="two"
    options={optionsForTwo}
    onChange={onChange}
  />

I don't want to create any unnecessary API differences between this project and react-select. I'd like for it to be a drop-in replacement in most cases; changing the argument signature of onChange would prevent that.

My current workaround is to create a handler which uses a closure to track the name.
_createChangeHandler(name) {
  const onChange = (newValue) => this.setState({ [name]: newValue.value });
  return onChange;
}

const onChange = this._createChangeHandler(name);
return (
  <Select
    name={name}
    value={this.state[name]}
    onChange={onChange}
    ...
  />
);

Opened an issue upstream https://github.com/JedWatson/react-select/issues/1458


Allowing/optimizing RGB image retrieving

Previously, the returned image of RGBCamera is the grayscale image. Now, we add a configrgb_to_grayscale to allow returning RGB image.

Please describe why you create this PR

Checklist

[ ] I have merged the latest main branch into current branch.
[ ] I have run bash scripts/format.sh before merging.
Please use "squash and merge" mode.

Link #207


Usability fixes

What it does, and why
DESIGN-239 and DESIGN-218 fixes:

Fix Select styling -- border-radius, colour, padding
Fix Small element and props
Add uppercase prop to Typography
Fix Grid and Flex default props
Fix Sidebar filter badge alignment

Jira cards:
https://orchestrated.atlassian.net/browse/DESIGN-239
https://orchestrated.atlassian.net/browse/DESIGN-218

Now on modal, clicking the overlay background closes the modal, but clicking the cross does not.
and default align-items for flex component needs to be fixed.
Other than that it looks good to me.

Re: default prop for align-items, I went by this: https://developer.mozilla.org/en-US/docs/Web/CSS/align-items
Re: the X bug, thanks for the catch -- I've updated the code in Modal.stories.js (basically, if you're using useEffect you have to add an event listener to the X as well, and no need to use onClick)


Add a proper Cube save format

Currently the save format is just a testing thing, and should most likely be rewritten from 1.12

This has two options:

Have the file format save as the current cube size as specified in the config. Reinterpret that if save cube size != config cube size
Have the file format save as cube ambiguous. Each time a world is started, it will correctly interpret that as the cube size specified in the config.

The former is most likely better in many situations.

I am going to implement an indev save format to test tileentities, biomes, etc

Indev save format "finished" in https://github.com/OpenCubicChunks/CubicChunks/commit/ae5fd1385fdc2e3b9a647fb82ba79ba9278d8f32

Closed by commits from 2660c5e25931b4a1b76b0e52e52db71ad98e15bc to 96b45e505a9080cb749c2f4302ce38b85a81b025. Was later merged to 1.17 too


[web] Connect Page Data Fetching Refactor for Perf

This is Ported over from https://github.com/celo-org/celo-monorepo-old/pull/4240
Description
This moves data fetching for connect/community page to happen via express routes after page has loaded instead of in getInitialProps. This has three benefits

code and libraries for fetching are not loaded on client reducing page load size
no need to wait on our server to wait for third party API to return, thus speeding up our TTFB
data is always loaded the same way (fetch on mount of component that needs it) thus fixing a bug where if we navigated to page via a link the medium articles wouldn't load due to CSRF.

Tested

version
Total Bytes
Unused Bytes
percent unused
Dev or Prod
what changed

0
4 540 492
3 709 591
81.7 %
dev
base a9ffacd2fbae1b3458bc3bbe2bc137e42870c7ce

1
2 810 549
2 102 538
74.8 %
Dev
moved data fetching code to only load serverside

Other changes
add loading option to Events for better UI
This version fixes Postevents page import issue by converting to same data loading method as connect page for events

https://github.com/celo-org/celo-monorepo/issues/28


The Starship creator gave me a runabout that uses d6/starfleet delta dices instead of the 2e damage rating

So, I'm creating a Runabout from the year 2600 that uses Chroniton Torpedoes and Graviton Beams, but for some reason it gave me d6 dices for the damage rating instead of the damage rating of second edition. Is this like a bug or something?

You're right. That's a bug. Good catch!

Should be fixed, now.


[New Port Request] luxcorerender

Library name: LuxCoreRender
Library description: LuxCore is the new LuxCoreRender v2.x C++ and Python API. It is released under Apache Public License v2.0 and can be freely used in open source and commercial applications.
Source repository URL: https://github.com/LuxCoreRender/LuxCore
Project homepage (if different from the source repository): https://wiki.luxcorerender.org/LuxCore_API
Anything else that is useful to know when adding (such as optional features the library may have that should be included):
Official Website: https://www.luxcorerender.org/

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


ModuleErrorNotFound for some installed packages

Issue Type: Bug
1.Create virtual environment.
2.Install flask. Run code on cmd and vscode to import flask. Successful result.
3.Create simple module. Import module in vscode. Successful result.
4.Install tensorflow, pendulum, and pandas. Execute code in cmd to import packages and print version. Successful result.
5.Import packages in vscode. Encounter ModuleNotFoundError .
For some reason the installed packages work when I execute them on CMD but not in VSCODE. I'm not using Anaconda.
Using python 3.8.5.
Extension version: 2021.1.502429796
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.86GB (2.05GB free)

Process Argv
--crash-reporter-id d4a77182-647a-4bc2-a7c0-a9d197e52577

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
pythonvspyt617cf:30253240
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry914:30256638
pythonvsdeb440:30248342
pythonvsded773:30248341
vstes627:30244334
pythonvspyt600cf:30251589

I tried using jupyter notebook and my code worked. A simple:
import tensorflow as tf
print(tf.version)
I've read that you don't necessarily have to have jupyter for tensorflow to work but I can't seem to make it run on pure vscode .py file.

@jonathanH1983 Is the environment activated? Can you try and start vscode from an activated environment using code . to launch it?

I have always activated my environment when I encountered my problem (venv\scripts\activate).
Not sure if I did this right cos I'm not familiar with "code ." but this is what I did from CMD after activating the virtual environment and it launched VSCODE:
(venv) C:\Users\Jonathan\Documents\Programming Folder\Scratch>code .
After VSCODE finished loading the extensions I was able to successfully execute a simple tensorflow code:
import tensorflow as tf
print(tf.version)
Output: Code
2021-02-18 17:51:26.495267: W tensorflow/stream_executor/platform/default/dso_loader.cc:60] Could not load dynamic library 'cudart64_110.dll'; dlerror: cudart64_110.dll not found
2021-02-18 17:51:26.515115: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.
2.4.1
I understand that the first 2 messages can be ignored since I have not set up my cuda but I was able to get the version out this time.
Do I use "code ." from now on? What does this syntax mean?

code . the 'dot' means current directory. That command is just launching VS Code from which ever directory you are in. You will only need to do this if the environment is not getting activated from VS Code correctly.

OK. I'll guess I just have to do use this each time I encounter this problem. Thanks a lot!

@jonathanH1983 We have plans to address the issue with failing activations. This is a just a workaround until we are able to fix it entirely.


Arm64: function arguments/register definitions broken

Hello!
I am currently using bpftrace/bcc on arm64(Yocto, Kernel version 4.14.35), for a small paper to correlate some latency measurements.
It's holding up very nice, and I'm getting some nice data from it, but I encountered some weirdness on my test machine and wanted to report that.
It seems to me that the function argument handling for kprobes/the register definitions for arm64 are not correct/non-existent:
root@arm64qemu:~# bpftrace -e 'kprobe:do_sys_open { printf("%s: %s\n", comm, str(arg1)) }'
Attaching 1 probe...
touch:
touch:
touch:
<-snip>

It might have something to do with bpftrace not recognizing the architecture(Which could be a compile error on my side?):
root@arm64-qemu:~# bpftrace -e 'kprobe:do_sys_open { printf("%s: %s\n", comm, str(reg("r16"))) }'
'r16' is not a valid register on this architecture (x86_64)

For now, one workaround i found is to use the x86_64 register definitions, and just correlate register positions somehow to the armv8 registers containing the function arguments: (arg0->r15,arg1->r14,...)
root@arm64-qemu:~# bpftrace -e 'kprobe:do_sys_open { printf("%s: %s\n", comm, str(reg("r14"))) }'
Attaching 1 probe...
touch: /usr/local/lib/tls/aarch64/cpuid/libc.so.6
touch: /usr/local/lib/tls/aarch64/libc.so.6
<...>
touch: /lib/libc.so.6
touch: /tmp/foo

As I found no aarch64 register definitions in "src/arch/", I assume this for now is a missing feature and wanted to post the workaround - if my compile is broken, please correct me!
Greetings,
Brother Lal

This seems pretty straightforward. I'll work on a patch

#393 successfully builds in the docker container on an Arm host and the command above works correctly:
$ uname -m
aarch64

$ sudo ./bpftrace -e 'kprobe:do_sys_open { printf("%s: %s\n", comm, str(arg1)) }'

Attaching 1 probe...
irqbalance: /proc/interrupts
irqbalance: /proc/stat
irqbalance: /proc/irq/2/smp_affinity
irqbalance: /proc/irq/9/smp_affinity
irqbalance: /proc/irq/10/smp_affinity

All,
As the below command , I can not access the register, so is that possible to access register on android.
bpftrace --unsafe -e 'kprobe:sched_fork+0xD8 {printf("the state is \n", str(reg("r9")))}'
thank you very much.


Add support for armv5te-unknown-linux-gnueabi

@alexcrichton has the update containing this change landed? I'd like to resolve the related FIXME. I'd also like to know if only lines 107-110 should be removed or anything else too?

@ljedrz yes this should be published

Can you please advise if only lines 107-110 should be removed or anything else too?

Yes those can probably be removed now, unsure about others. Best way to find out is to test it!


[TC-435] TPv2 - add the ability to clone DS assignments from one server to another

Add the ability to clone DS assignments from one server to another.
Author: Jeremy Mitchell
JIRA Link: https://issues.apache.org/jira/browse/TC-435

@DylanVolz has been working on this. @DylanVolz can you add a comment that links this issue to your PR?

#1197 addresses the api changes needed for this issue.

this is done


Use GMT offset as channel name

This partially fixes the issue where certain time zones will never receive push notifications because the time zone names used by Rails are different from those used by iOS (See thoughtbot/Tropos#185 for more information)
This fixes it by not using the names, but the relative offset from UTC as the channel name. Currently we subscribe to us-pacific when the iOS time zone is set to San Francisco.
This PR changes it to subscribe to the channel minus-0700 instead. This is a more reliable way of identifying time zones across platforms.

Closing because this should be against kp-release branch.


Self-hosted extractors: Mastodon, PeerTube and Misskey (with haruhi-dl merge)

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[x] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

Both are intentionally checked because some code from this PR includes the code from haruhi-dl and #1505.
What is the purpose of your pull request?

[ ] Bug fix
[x] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
This PR adds support for 3 self-hosted services: Mastodon, PeerTube, Misskey
Also, this replaces GabIE with MastodonIE.
supersedes #1505, #4609
cc @selfisekai
TOC

Extractors

additional extractor for some instances (only Misskey)

Instance lists
Script to update instance list above
some other things

TODO

[ ] where to go: To download videos from Gab Social or Truth Social, use --ies mastodon.*,generic.
[x] handling of currently failing tests (because it lacks instance list that are assumed to exist in the tree)

I think the probe should first try fetching the instance's NodeInfo, which is a standard used in all of these services (and more of fediverse, see the standard's webpage; excluding Gab, for unknown to me reason, but it's not really a selfhosted service and it's always on the instance list) and allows to just see the software name and supported features

also to be added to scrapers where possible:
mastodon: akkoma (fork of pleroma), rebased (soapbox-be; fork of pleroma), hometown (fork of mastodon)
misskey: foundkey (fork), calckey (fork)

@selfisekai with the current code, these forks are detected as their respective extractors (including instance checks), so it look okay fir now
if there are anything to be done particularly for these forks, they're TBD in the future

Fallback instance lists will now have required ones for passing tests

Any news on this PR? :)
PeerTube relies heavily on yt-dlp to import remote channels/videos/playlists. It would be nice if the software could automatically detect a peertube, as we are limited for now by the URLs list written directly in the code.

ugh, afaik the PR author is in jail, lmao


changed create_filemgmt_links script and added jbpm

Merged into master: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/commit/fb52da0aba0fe0feb10a96de3d41301ee728ed91