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

CRASH: project_1.jsTSConfig is not a function #969

Open
johanms opened this issue Aug 9, 2021 · 1 comment
Open

CRASH: project_1.jsTSConfig is not a function #969

johanms opened this issue Aug 9, 2021 · 1 comment

Comments

@johanms
Copy link

johanms commented Aug 9, 2021

Error Report

I get this error when running yarn bigtest server --launch=chrome after upgrading from bigtest 0.13.3 to 0.14.1:

TypeError: project_1.jsTSConfig is not a function

diagnostics

Argv

server,--launch=chrome

Stack

TypeError: project_1.jsTSConfig is not a function
at prepareInputOptions (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/@bigtest/bundler/dist/bundler.js:54:89)
at prepareWatchOptions (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/@bigtest/bundler/dist/bundler.js:87:12)
at Bundler.watch (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/@bigtest/bundler/dist/bundler.js:114:37)
at watch.next ()
at /Users/johanms/workspace/fleks/fleks-marketing/node_modules/effection/dist/effection.js:1:7739
at e.r.advance (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/effection/dist/effection.js:1:7781)
at e.r.enter (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/effection/dist/effection.js:1:7701)
at t.call (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/effection/dist/effection.js:1:8325)
at t.n.enter (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/effection/dist/effection.js:1:4576)
at t.call (/Users/johanms/workspace/fleks/fleks-marketing/node_modules/effection/dist/effection.js:1:9495)

@cowboyd
Copy link
Member

cowboyd commented Aug 9, 2021

Thanks @johanms for the bug report! I suspect that it might be related to a recently introduced change: #961

@dagda1 dagda1 mentioned this issue Aug 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants