Add nextjs-server framework

[shilman]

Extract @storybook/nextjs-server from storybookjs/storybook#24447

• Delete some dead code
• Add necessary scripts for building & type checking
• Update indexing code to work with existing indexer API

Required SB core changes are here: storybookjs/storybook#25086

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
next	14.0.3	eval, network, filesystem, shell, environment	+6	88 MB	vercel-release-bot
tsup	6.7.0	eval, filesystem, environment	+3	1.79 MB	egoist

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Shell access	@aw-web-design/x-default-browser	1.4.126	Module: child_process Location: src/detect-linux.js +2 more instances...	@storybook/core-server@0.0.0-pr-25086-sha-fa16f873 via packages/nextjs-server/package.json
Shell access	next	14.0.3	Module: child_process Location: dist/cli/next-dev.js +24 more instances...	packages/nextjs-server/package.json
Telemetry	next	14.0.3	Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information	packages/nextjs-server/package.json
Uses eval	next	14.0.3	Eval Type: Function Location: dist/compiled/@babel/runtime/regenerator/index.js +56 more instances...	packages/nextjs-server/package.json
Shell access	update-browserslist-db	1.0.13	Module: child_process Location: check-npm-version.js +1 more instances...	@babel/core@7.23.5, next@14.0.3 via packages/nextjs-server/package.json
Uses eval	tsup	6.7.0	Eval Type: Function Location: dist/chunk-OSC67C6M.js +1 more instances...	scripts/package.json

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is telemetry?

This package contains telemetry which tracks how it is used.

Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore next@14.0.3
• @SocketSecurity ignore tsup@6.7.0
• @SocketSecurity ignore @aw-web-design/x-default-browser@1.4.126
• @SocketSecurity ignore update-browserslist-db@1.0.13