Comments (4)
The message may be misleading, as the logs the following errors are present:
Module "child_process" has been externalized for browser compatibility. Cannot access "child_process.spawn" in client code. See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
Module "child_process" has been externalized for browser compatibility. Cannot access "child_process.exec" in client code. See https://vitejs.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
This appears to have been introduced in the following PR (based upon the CI failures):
I can imagine that there is failure path that is causing child_process
to be called in the browser env, not 💯 sure where yet.
cc @nedsalk
from fuels-ts.
Indeed child_process
will not work in browser. When bundling, every time vite
identifies that dep it'll give that warning. However, we should be dynamically importing it everywhere it is actually needed in tests. I'd expect it to throw on that line otherwise, like it did in the past before we had a dynamic import.
We could try the v8
coverage provider.
from fuels-ts.
Bumping priority to p0
as it seems to affect everything else. cc @nedsalk
from fuels-ts.
I see that some of the CI jobs are now passing upon re-running the jobs, so the PRs in my description may become outdated.
from fuels-ts.
Related Issues (20)
- Integrate `launchTestNode` into templates HOT 1
- Multiple wallets with individual configs in `launchTestNode` HOT 6
- Add pagination support for `getBalances` HOT 1
- Add `doc-comment` attribute support for `typegen` outputs
- `create fuels` template broken metadata
- `launchTestNode` should infer contracts sequentially
- `fuels build` throws `Dynamic require of "@fuel-ts/script" is not supported` error HOT 1
- Consistent `currentConnector` return type HOT 1
- Empty operation being returned in txSummary
- Debug `waitForResult` integration test
- Improve faucet integration in `create fuels` HOT 1
- Add type-level tests for `launchTestNode` HOT 1
- `create fuels` does not automatically install dependencies anymore
- Migrate `create fuels` template from NextJS to Vite
- Remove all state from default `stateConfig.json`
- Allow passing of `Uint8Array` for `Vec<u8>` in typegen
- Support `Uint16Array` for `Vec<u16>` and `Uint32Array` for `Vec<u32>`
- Add validation around `programType` in relevant places HOT 2
- Make `Option<x>` optional with typegen
- Make configurable properties optional in typegen outputs
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fuels-ts.