Open DamienCassou opened 2 years ago
Also being bitten by this, using yarn. Took me ages to figure out where the issue originated and finding this issue. Seems like a definite bug.
Also experiencing this issue using yarn :/ Yarn version: 1.22.19 Node version 14.20.0
Adding @babel/preset-typescript
as a devDependency did the trick. Thanks for the workaround!
Running into the same issue. Is it possible to make it at least not bundle the React dependency, as I'm running this in a Vue project?
Running into the same issue. Is it possible to make it at least not bundle the React dependency, as I'm running this in a Vue project?
+1
The same issue. Workaround in this topic helped
Describe the bug
It seems that
@babel/core
and babel presets referenced fromplaywright/transform.js
should be added todependencies
orpeerDependencies
in yourpackage.json
.This is not a problem for most people because babel dependencies will be available at the root of
node_modules/
anyway but it becomes a problem when the package manager (yarn
in my case) decides to move babel packages to where they are used instead of the top-level:/project/node_modules/@storybook/core-common/node_modules/@babel/preset-typescript
/project/node_modules/jscodeshift/node_modules/@babel/preset-typescript
Workaround
As a workaround, users facing this issue can declare these dependencies in their own
package.json
:Environment