Jack Works
Jack Works
Ok, it is because I forgot to remove the `"browser"` field in the `package.json` of `@emotion/styled`. Now it works to get some CSS output, (but the render is still broken).
I'd like to share our use case on this issue. We have a single application that builds multiple times with different flags. This is what I do: build the `base`...
hmm sorry but I'm still waiting for this
The trick mentioned above `--prefix=/dev/null` doesn't work in npm7. I prepared a new empty npm project (`./empty/package.json`) and use that `--prefix=/empty`
@hotyes > netlify.toml ```toml [build] command = "./scripts/netlify.sh" [build.environment] NPM_FLAGS="--prefix=./scripts/empty-project/" ``` > scripts/netlify.sh ```sh #!/bin/bash set -xeuo pipefail test "$CI" = true || exit 1 npx pnpm install -r --store-dir=node_modules/.pnpm-store...
If we allowing this, we can use it to use npm v6 for projects that don't want to upgrade lockfile to v2. e.g.: https://github.com/microsoft/TypeScript/blob/f8aa570b23bd094798a98cef307038b1da9101a7/package.json#L31 > "packageManager": "[email protected]", This does not...
I think this problem happens in storybook 6 again
> @Jack-Works Did you solve your issue in Storybook 6? Yes, but I didn't remember how. Maybe some special command line argument
Hot path is the code being executed most frequently