You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The values are the actual handler files that are the entry points defined by your service, which are determined by the Serverless service. I agree that, if you have a TS handler, it should point to the ts file and should not stupidly append .js to the handler base file name, but check for the file itself and set the correct path to the actual file (ts, js or something else) as value. This should be done automatically by the plugin.
The keys should behave the same -> if you are using ts the key should end with ts. As a user you know what your service configuration is, so it will then be quite easy to replace it via regex if you want a non-standard special behavior.
After some thinking, the keys should not add the extension, because of the filename modification you mentioned above.
This is a Bug Report
Description
slsw.lib.entries
returns an object with keysname.js
, and as values the string./name.js
.This is making developing with typescript quite difficult:
[name].[hash].js
, or in case I actually want a different extension.Additional Data
The text was updated successfully, but these errors were encountered: