Using an external JSON file to define options for a list in a Sanity schema file

import skills from '../../web/src/_data/skills';

"default" is not exported by "../web/src/_data/skills.js", imported by "schemas/project.ts".

import { skills } from '../../

{
  "compilerOptions": {
    "target": "ES2017",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true
  },
  "include": ["**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules"]
}

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "esnext",    
    "outDir": "dist", 
    "jsx": "preserve",
    "lib": ["es6", "dom", "es2015", "es2017"],
    "strict": true, 
    "isolatedModules": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "removeComments": true,
    "preserveConstEnums": true,
    "noImplicitAny": true,
    "noImplicitThis": true,
    "strictNullChecks": true,
  },
  "include": ["**/*.ts", "**/*.tsx"],
  "exclude": ["node_modules", "sanity.cli.ts", "sanity.config.ts"]
}

Hey GPT, do I have to set module to commonjs to use default and named imports and exports?

FROM GPT
No, you do not have to set the module option to commonjs in order to use default and named imports and exports.

ES6 module syntax (import and export) can be used with other module formats as well, such as amd, umd, and system. However, in order to use ES6 module syntax with Node.js, you'll need to transpile the <https://www.sanity.io/typescript-guide/typescript-vs-javascript|typescript> code into a format that's compatible with Node.js, such as CommonJS. This is why setting the module option to commonjs is a common practice when developing Node.js applications with <https://www.sanity.io/typescript-guide/typescript-vs-javascript|typescript>.

In general, you can choose the module format that works best for your specific use case, and configure the module option in <https://www.sanity.io/typescript-guide/typescript-vs-javascript|typescript> accordingly. Just keep in mind that the output JavaScript code needs to be compatible with the module format that you choose.