ts-node seems can not require json file

[notedit]

one of my config module like this

export interface ConfigSetting {
// some code 
}
export const config : ConfigSetting  = require('./config.json')

tsc compiles well.

when i use ts-node, it has some error like

let db = new Sequelize(config.database)
                             ^
TypeError: Cannot read property 'database' of undefined

[blakeembrey]

A type error is an actual JavaScript error at runtime. It's nothing to do with ts-node. Just because you tell the compiler something is true, doesn't mean it actually is at runtime. That error is because config is undefined during runtime. If you'd like more help, you'll need to share a reproduction.

[notedit]

@blakeembrey i just create a test repo to reproduct what i say.

https://github.com/notedit/test-ts-node

i am new to ts, maybe i made a silly mistake.

[notedit]

ts-node  server.ts   will have an error,  

tsc  &&  node server.js  works fine 

[notedit]

@blakeembrey can you have a look?

[blakeembrey]

This is (unfortunately) expected. You've named your .ts and .json file the same, .json has higher precedence than .ts. .js has higher precedence than .json.

[freewind]

@blakeembrey Please see my demo of this issue: https://github.com/freewind-demos/ts-node-import-json-file-issue-demo, I don't name .ts and .json file the same name, but there is the same error

[freewind]

I fixed my demo by adding "resolveJsonModule": true, to tsconfig.json, see: freewind-demos/ts-node-import-json-file-issue-demo@0f9e472

PS: resolveJsonModule is supported by typescript 2.9+ only, so old versions still have such issue

[charleston10]

@freewind thanks it worked for me

[donaldoakes]

This worked for me to prefer .ts over .json for same-named files:

export TS_NODE_PREFER_TS_EXTS=true