js emit is outdated

[fcoury]

What does this warning means and how to fix it?

[basarat]

@fcoury Press ctrl+s to emit a .js file corresponding to the .ts file

[faisalnet5]

I am also seeing the same warning message. Did try pressing ctrl+s to emit a .js file corresponding to the .ts file...but still no difference.

Any more clue plz?

[basarat]

Did try pressing ctrl+s to emit a .js file corresponding to the .ts file.

Did the .js file change when you saved it? Try deleting it and seeing if saving the .ts brings back the .js file.

Also what is you tsconfig.json. Thanks 🌹

[faisalnet5]

Hi Basaerat, thanks for ur reply. Yes..I did try all as u suggested. First of all when I am changing .ts, the .js is changing only when I am saving .ts and recompiling it through tsc compiler.

I also tried to delete .js entirely and generate a fresh one.

However in all cases that Warning message 'Js emit is outdated' is appearing. Particularly noticed that as soon as when typing any new code that Warning appears.

Btw, do you think that is any important issue? Because for that Warning, me not having or at least for now not seeing any other exceptions though.

Lastly, here is my sample 'tsconfig.json':

{
"compilerOptions": {
"module": "commonjs",
"noImplicitAny": true,
"removeComments": true,
"preserveConstEnums": true,
"out": "C:/Users/AnyName/Desktop/Play/greeter.js",
"sourceMap": true
},
"files": [
"greeter.js"
]
}


Thanks

[faisalnet5]

Basaerat, its me again....this morning I got two updates and one of them was from 'atom-typescript'. After installing update and restarting Atom, everything looks fine at my end.

Dont know whether there is any relationship or not ;)

[basarat]

""out": "C:/Users/AnyName/Desktop/Play/greeter.js" we have poor out support, specifically compileOnSave doesn't work tracked here : #206

[dcsan]

see this too on osx

does it mean the tscnofig.json file itself is outdated, or some other output is not up to date.

I used F6 to rebuild all, but no change to this error message.

[dcsan]

tsc itself from cmd line also compiles cleanly.

when i open the .tsconfig the error above is not shown, it only appears on toggling back to a .ts file.

{
    "buildOnSave": true,
    "scripts": {
        "postbuild": "echo after building"
    },
    "compilerOptions": {
        "target": "es5",
        "declaration": true,
        "noImplicitAny": false,
        "removeComments": false,
        "module": "commonJS",
        "noLib": false,
        "sourceMap": true,
        "newLine": "LF"
    },
    "filesGlob": [
        "./src/**/*.ts",
        "./src/*.ts",
        "!./node_modules/**/*.ts"
    ],
    "files": [
        "./src/adapters/BaseAdapter.d.ts",
        "./src/adapters/BaseAdapter.ts",
        "./src/adapters/CurrentAdapter.d.ts",
   ... bunch of files

[basarat]

"buildOnSave": true,

Digression: @dcsan Don't recommend using buildOnSave if you are not using --out (which you are not).

does it mean the tscnofig.json file itself is outdated, or some other output is not up to date.

It means the current file's .js emit is not the same as what would be generated if we compile the .ts to .js again.

[basarat]

everything looks fine at my end.

Should have closed then. Closing now 🌹

@dcsan if your questions aren't answered, feel free to continue discussion here

[doliver3]

1. Why does the js get outdated
2. Why is the error displayed in red as if it is a programmer's error. It is not a programmers error if I understand right. It is an indication that the tool is not keeping up with the compilation it needs to do so the styling should not be a red x nor should it imply as it does now the that the programmer has an issue to fix.