
Research
/Security News
GlassWASM: WebAssembly Malware Found in Trojanized Open VSX Extensions
The trojanized extensions use TinyGo-compiled WebAssembly and Solana transaction memos to resolve command-and-control infrastructure.
@nestpress/next
Advanced tools
😎 @nestpress/next 😎
The Next.js integration module for NestJS
$ npm install --save @nestpress/next
First, populate package.json, tsconfig.json and tsconfig.server.json:
{
"name": "sample-app",
"scripts": {
"dev": "ts-node -p tsconfig.server.json server/main.ts",
"build": "next build && tsc -p tsconfig.server.json",
"start": "cross-env NODE_ENV=production node .next/production-server/main.js"
},
"dependencies": {
"@nestjs/common": "^6.6.7",
"@nestjs/core": "^6.6.7",
"@nestpress/next": "latest",
"next": "^9.0.5",
"react": "^16.9.0",
"react-dom": "^16.9.0",
"reflect-metadata": "^0.1.13",
"rxjs": "^6.5.3"
},
"devDependencies": {
"@types/node": "^12.7.5",
"@types/react": "^16.9.2",
"@types/react-dom": "^16.9.0",
"cross-env": "^5.2.1",
"ts-node": "^8.3.0",
"typescript": "^3.6.3"
}
}
{
"compilerOptions": {
"target": "esnext",
"module": "esnext",
"moduleResolution": "node",
"jsx": "preserve",
"lib": [
"dom",
"dom.iterable",
"esnext"
],
"strict": true,
"noEmit": true,
"allowJs": true,
"skipLibCheck": true,
"esModuleInterop": true,
"isolatedModules": true,
"resolveJsonModule": true,
"forceConsistentCasingInFileNames": true,
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"incremental": true
},
"include": [
"next-env.d.ts",
"**/*.ts",
"**/*.tsx"
],
"exclude": [
"node_modules"
]
}
{
"extends": "./tsconfig.json",
"compilerOptions": {
"module": "commonjs",
"noEmit": false,
"outDir": ".next/production-server"
},
"include": [
"server"
]
}
Register NextModule in your application module so that the Nest can handle dependencies:
import {
Module,
NestModule,
MiddlewareConsumer,
RequestMethod,
} from '@nestjs/common';
import {
NextModule,
NextMiddleware,
} from '@nestpress/next';
import { AppController } from './app.controller';
@Module({
imports: [
// register NextModule
NextModule,
],
controllers: [
AppController,
],
})
export class AppModule implements NestModule {
configure(consumer: MiddlewareConsumer) {
// handle scripts
consumer
.apply(NextMiddleware)
.forRoutes({
path: '_next*',
method: RequestMethod.GET,
});
// handle static assets
consumer
.apply(NextMiddleware)
.forRoutes({
path: 'static*',
method: RequestMethod.GET,
});
}
}
Prepare the Next.js service in the main entry point:
import { NestFactory } from '@nestjs/core';
import { NextModule } from '@nestpress/next';
import { AppModule } from './app.module';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
app.get(NextModule).prepare().then(() => {
app.listen(3000, '0.0.0.0', () => {
console.log('> Ready on http://localhost:3000 with Next.js!');
});
});
}
bootstrap();
Use NextService in your controllers like this:
import {
IncomingMessage,
ServerResponse,
} from 'http';
import {
Controller,
Get,
Req,
Res,
} from '@nestjs/common';
import { NextService } from '@nestpress/next';
@Controller()
export class HomeController {
constructor(
private readonly next: NextService,
) {}
@Get()
public async showHome(@Req() req: IncomingMessage, @Res() res: ServerResponse) {
// this will render `pages/index.tsx`!
this.next.render('/index', req, res);
}
}
In the pages directory, we can do the same as the Next.js way:
export default () => (
<p>Next.js on top of NestJS!</p>
);
$ yarn dev (or `npm run dev`)
Go to http://localhost:3000 and you'll see Next.js on top of NestJS!.
$ yarn build (or `npm run build`)
$ yarn start (or `npm start`)
FAQs
The Next.js integration module for NestJS
We found that @nestpress/next demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
/Security News
The trojanized extensions use TinyGo-compiled WebAssembly and Solana transaction memos to resolve command-and-control infrastructure.

Security News
Anthropic says the directive cited national security concerns over a narrow jailbreak, but offered no specific technical details.

Security News
A network of 152 Chrome live wallpaper extensions hid ad tracking and made extension-driven traffic look like Google search clicks.