Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode extension editor's "Test Flow" conflicted with existing tsconfig #114

Open
its-frank-huang opened this issue Apr 12, 2024 · 1 comment
Labels
bug Something isn't working investigating

Comments

@its-frank-huang
Copy link

Problem

When I click the "Test Flow" button, an error will appear

Unexpected error while handling message from webview: 
Could not find Custom Add in {absolute path to project}/add.flyde.ts. 
The following errors were thrown, and might be the reason the node is not properly resolved. 
Errors: Error loading module "{absolute path to project}/add.flyde.ts": Unexpected token 'export'

Possible Cause

After some fiddling around, I found out that changing the module to NodeNext and moduleResolution to NodeNext seems to make it work

Steps to Reproduce

  1. Init a regular npm project
  2. Install @flyde/core using package manager
  3. Create a Flyde flow
  4. Add a custom code node (the add in the tutorial will do)
  5. Import the custom code node
  6. Click "Test Flow" (it should work)
  7. Create a tsconfig.json
  8. Change module to ESNext and moduleResolution to ESNext
  9. Click "Test Flow" (expected to fail)

Request

monorepo doesn't work either

@GabiGrin
Copy link
Contributor

Hey @its-frank-huang, thanks for the report and the suggested cause.
Does using "NodeNext" unblock you for now?

@GabiGrin GabiGrin added bug Something isn't working investigating labels Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working investigating
Projects
None yet
Development

No branches or pull requests

2 participants