This option disables key expiration requiring the user to manually manage key cleanup outside of connect-redis. Also consider enabling if you store a lot of data on the session.ĭisables key expiration completely (default: false) Typically, this helps keep the users session alive if session changes are infrequent but you may want to disable it to cut down the extra calls or to prevent users from keeping sessions open too long. The express-session package uses touch to signal to the store that the user has interacted with the session but hasn't changed anything in its data. disableTouchĭisables resetting the TTL when using touch (default: false) Calling session.save() manually beforehand will have the previous value. Note: express-session does not update expires until the end of the request life cycle. You can disable this behavior in some instances by using disableTouch. Note: The TTL is reset every time a user interacts with the server. You can use it for dynamic TTL generation. You would need to pay attention to module import order though.Import RedisStore from 'connect-redis' import session from 'express-session' import It would be additive and you wouldn't need to worry if the file has an import/export statement, or whether mocha/ts-node/etc has the -files option set to prevent the files array in your tsconfig.json from being wiped out. You could instead put an augmentation in each module that creates a new field on the session. If you augment inside of a normal module, instead of a declaration, there's no need to do any extra imports. It's converting the way typescript handles module declarations i.e. Adding the import statement is simply turning the file into a module. You could simply add export and it would have the same effect. On the other hand, if the file is considered a module then you will be 'augmenting' the module declaration. ts), if the file is not a module, module declarations will overwrite the entire module, essentially zeroing out everything not explicitly added. I would like to point out that adding import 'express-session' to the typings file is solving the issue, but probably not how you think. d.ts file and edit SessionData it works file. server/routes/site.ts(9,11): error TS2339: Property ' session ' does not exist on type ' Request >'.īut when I make a copy of and paste it to the.

server/routes/site.ts(8,28): error TS2339: Property ' session ' does not exist on type ' Request > '. server/routes/site.ts(8,12): error TS2339: Property ' session ' does not exist on type ' Request > '.

server/routes/auth.ts(76,7): error TS2339: Property ' session ' does not exist on type ' Request > '. server/routes/auth.ts(44,7): error TS2339: Property ' session ' does not exist on type ' Request > '. server/routes/auth.ts(17,7): error TS2339: Property ' session ' does not exist on type ' Request > '. server/routes/auth.ts(13,9): error TS2339: Property ' session ' does not exist on type ' Request > '. server/routes/auth.ts(10,46): error TS2339: Property ' session ' does not exist on type ' Request > '. server/routes/auth.ts(9,28): error TS2339: Property ' session ' does not exist on type ' Request > '. server/routes/auth.ts(9,12): error TS2339: Property ' session ' does not exist on type ' Request > '. Type ' typeof import ( ) ' has no call signatures. server/index.ts(57,5): error TS2349: This expression is not callable. Type ' typeof import ( ) ' provides no match for the signature ' ( options?: any ): RequestHandler > '. ts ( 55, 35 ): error TS2345: Argument of type 'typeof is not assignable to parameter of type '(options?: any) => RequestHandler>'.

Express session typescript