ef1d772447
Summary: Fixes https://github.com/facebook/yoga/issues/1417 This dramatically simplifies the matrix of Node vs web, ASM vs WASM, sync vs async compilation, or CommonJS vs ES Modules. We have one variant, using wasm, with ESModule top-level await to do async compilation. Web/node share the same binary, and we base64 encode the WASM into a wrapper JS file for compatibility with Node and bundlers. This has some downsides, like requiring an environment with top level await, but also has upsides, like a consistent, sync looking API compatible with older Yoga, and mitigating TypeScript issues with package exports and typings resolution. As part of this work I also removed `ts-node` from the toolchain (at the cost of a couple of config files needing to be vanilla JS). Pull Request resolved: https://github.com/facebook/yoga/pull/1433 Test Plan: 1. `yarn test` 2. `yarn lint` 3. `yarn tsc` 4. `yarn benchmark` 5. `yarn build` website-next 6. `yarn lint` website-next 7. Locally test website-next 8. Examine package artifact created by GitHub 9. All Automation passes Reviewed By: yungsters Differential Revision: D50453324 Pulled By: NickGerleman fbshipit-source-id: fe1192acc69e57fa69a1ff056dd7b5844d2198d5
24 lines
543 B
JSON
24 lines
543 B
JSON
{
|
|
"compilerOptions": {
|
|
"target": "es2020",
|
|
"module": "esnext",
|
|
"strict": true,
|
|
"declaration": true,
|
|
"esModuleInterop": true,
|
|
"skipLibCheck": true,
|
|
// TODO: moduleResolution: "nodenext" is buggy with this if the absolute
|
|
// path contains any capital letters
|
|
"forceConsistentCasingInFileNames": false,
|
|
"baseUrl": ".",
|
|
"moduleResolution": "nodenext",
|
|
"allowImportingTsExtensions": true,
|
|
"paths": {
|
|
"yoga-layout": ["src"]
|
|
}
|
|
},
|
|
"include": [
|
|
"src/**/*",
|
|
"tests/**/*"
|
|
]
|
|
}
|