CARVIEW |
Select Language
HTTP/2 200
content-type: text/html; charset=utf-8
date: Fri, 15 Aug 2025 12:37:12 GMT
permissions-policy: interest-cohort=()
strict-transport-security: max-age=31536000; includeSubDomains
server: nginx
cache-control: s-maxage=53373, max-age=0
x-powered-by: Next.js
etag: "746g0uvdhp7z5d"
content-encoding: gzip
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
referrer-policy: no-referrer-when-downgrade
content-security-policy: default-src 'self' http: https: ws: wss: data: blob: 'unsafe-eval' 'unsafe-inline'; frame-ancestors 'self';
vary: Accept-Encoding
x-cache: Miss from cloudfront
via: 1.1 0e077edae0164077a900619ab0f7924e.cloudfront.net (CloudFront)
x-amz-cf-pop: BOM78-P9
x-amz-cf-id: PrffSvp_jldFDKTAJZUXYeLTGsSraij_slw-FVMFKbCEaJxdWVsJQQ==
TypeScript | Modules and Namespaces in TypeScript | Question3
TypeScript
Interview Preparation
- Interview Preparation For Software Developers
- Must Coding Questions - Company-wise
- Must Do Coding Questions - Topic-wise
- Company-wise Practice Problems
- Company Preparation
- Competitive Programming
- Software Design-Patterns
- Company-wise Interview Experience
- Experienced - Interview Experiences
- Internship - Interview Experiences
TypeScript | Modules and Namespaces in TypeScript | Question3
Last Updated :
Discuss
Comments
Which of the following is a correct way to use a default export?
// In file: user.ts
export default class User {
name: string;
constructor(name: string) {
this.name = name;
}
}
// In another file
import User from "./user";
const user = new User("Pranjal");
Default exports must always use the import * syntax
Default exports require curly braces during import
This is the correct way to define and import a default export.
Default exports do not support classes.
This question is part of this quiz :
Modules and Namespaces in TypeScript QuizShare your thoughts in the comments

GeeksforGeeks
We use cookies to ensure you have the best browsing experience on our website. By using our site, you acknowledge that you have read and understood our Cookie Policy & Privacy Policy