Andrew M

This is happening to me no matter what TS version with transpileOnly=true. Tried 2.2.2, 2.3.3, and next. Seems like it must be a bug in awesome-typescript-loader.

I can confirm that the way to work with newer yarn versions is to follow this format for the URL: `https://gitpkg.now.sh/api/pkg.tgz?url=` + URI encoded path + `&commit=` + commit specifier

How can we move this forward? What changes need to be made to support use_frameworks? `react-native-firebase` is perhaps one of the most popular libraries and it has a hard requirement...

As a very temporary workaround you can roll back to `react-native-firebase` version `14.11.1` and remove `use_frameworks`, that's the last version of rnfirebase that can build without use_frameworks.

It would be conveneint to be able to specify workspace wide package versions in package.json by adding a little bit of functionality to the existing workspace protocol (`"my-workspace-pkg": "workspace:*"`.) I...

@niklasramo I'm trying to do something similar but am running into an issue. I have a grid and some, but not all, of those grid elements contain another grid. I...

This would be awesome! I just tried to set babel-plugin-styled-components up in my react-native project only to discover that displayName didn't work unfortunately.

I'm also curious about this. Seems quite useful but it seems that the primary maintainer hasn't really touched it for over a year now. @gcanti would you please weigh in...

I also have this question. I installed cursive to try it out and in a very basic hello world project it says "cannot resolve js/require". The Cursive website advertises "First...

Issues don't become invalid just because nobody has bothered to look at them.