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
Transforming a barebones file that imports types from a dependency causes that dependency to get imported, even if the types aren't used - and the runtime types aren't available.
In this particular case, I'm passing the annotate: false option to babel-plugin-flow-runtime to try and work around #202.
Babel generates the following from the above file, which imports the flow-aws-lambda package; this package exports types, but does not export runtime types. I could try and use @babel/register to work around this, but for my purposes I'd like to have babel spit out code that's directly executed by node, for auditing and deployment purposes.
Along these lines, it'd also be nice to be able to disable annotations for a specific function, but I think for now disabling annotations just for specific files in babel's rc file will suffice.
Which package versions are you using?
flow-runtime@0.17.0
babel-plugin-flow-runtime@0.19.0
The text was updated successfully, but these errors were encountered:
@gajus I might be able to find time to work on this, though I have looked at the code, and I'm not sure I'll have enough context to implement a solution. I'm somewhat partial to the workaround in #240 for my own use-cases, but I don't think it's a great solution for #239 for everyone.
This is a:
Which concerns:
Relates to #202.
What is the current behaviour?
Transforming a barebones file that imports types from a dependency causes that dependency to get imported, even if the types aren't used - and the runtime types aren't available.
In this particular case, I'm passing the
annotate: false
option tobabel-plugin-flow-runtime
to try and work around #202.Babel generates the following from the above file, which imports the
flow-aws-lambda
package; this package exports types, but does not export runtime types. I could try and use@babel/register
to work around this, but for my purposes I'd like to have babel spit out code that's directly executed bynode
, for auditing and deployment purposes.What is the expected behaviour?
Generate only those runtime types that actually get used (in this case, none), and omit the associated imports if any:
Along these lines, it'd also be nice to be able to disable annotations for a specific function, but I think for now disabling annotations just for specific files in babel's rc file will suffice.
Which package versions are you using?
flow-runtime@0.17.0
babel-plugin-flow-runtime@0.19.0
The text was updated successfully, but these errors were encountered: