prisma-labs/vscode-next

Prisma-Nextjs

Features

Automatically adds types to your Next.js page components if you use getStaticSideProps or getServerSideProps. The returned types can not be automatically inferred and passed to the page.

This extension also enables type safety in js code by leveraging JsDocs.

Requirements

A Project with next as a dependency in your package.json

Extension Settings

Name	Description	Default
WillLuke.nextjs.root	Option to set the path to a nextjs project
WillLuke.nextjs.hasPrompted	Hides Autotypes Prompt if it has been shown	false
WillLuke.nextjs.addTypesOnSave	Automatically add NextJS page types on save	false
WillLuke.debug	Debug the Extension	false

Trying it out

• Install the extension
• Install the example

git clone https://github.com/williamluke4/vscode-next-types-example
yarn

• Open VSCode
• Accept Autotypes Prompt

• Navigate to pages/songs/[id].tsx or pages/ssr-songs/[id].jsx
• Hit Save ctrl-s or ctrl-p then search types

Known Issues

• Workspaces not Supported

Development

Installing

git clone https://github.com/prisma-labs/vscode-next.git
cd vscode-next
yarn

Debugging/Developing

Use VSCode built in debugger and select Run Extension

Packaging

yarn pkg

vscode-next's Issues

Extension doing unproperly fixes on code

VS-Code adds and removes typescript code onFormat or onSave

Hey Devs! Hope you doing well!

So, I was using this extension on some projects and started to note that some of the code that I've written went missing, and some other had appeared. Took a long time to discover that the one to blame was this extension.

It is removing and adding props in typescript components, its not a ideal default configuration. I imagine more people will bump into this problem with they try this extension, maybe it would be better to let the user define if they want it or not.

Im uploading a video to you see whats going on: