4 ms·
Ask HN: Frustrated with installing libraries for new projects?
Every time I go to start a new project whether it be for next.js or a react or even django. I constantly feel like I have so many libraries and packages I need to install.
Am I the only frustrated by this problem?
- jordantplows 4y agoI feel like this guy every time and even though thats a only a minute 1:30. This add's up over time when you use it for several projects and don't want to go search for packages you have used hundreds of times. https://www.youtube.com/watch?v=PWQ3LnlU4xo https://www.youtube.com/watch?v=PWQ3LnlU4xo
- scottydelta 4y agoI spent the better part of last two days setting up the dev environment of an old react-native project. With so many different things involved with hundreds of version compatibility issues, it has been a nightmare.
- jordantplows 4y agoWas this just for packages and libraries? Can you share a breakdown of the workload?
- scottydelta 4y agoI had to fix following things to get it running: 1. Play services API level/sdk version(Play store doesn't accept apps below 30 API level, current is 32). 2. Gradle(used to compile app for android) version compatibility issues with API level 31. 3. Some npm packages are not compatible with Gradle version 7.0+ 4. Java/jdk on Mac M1 version issue, current version 18 is too new but Oracle doesnt provide version below 17 for M1 architecture. Had to use Openjdk@11. 5. Metro server version issues which acts as bridge between npm start and emulator running in android studio. 6. Changes in how arguments are defined in Android Manifest file. 7. Issues due to different kind of caches being created by android studio, gradle, node packages. 7. Figuring out the right combination of all the above things to work with each other.
- jordantplows 4y agoWow that's wild. Huge pain How did you solve some of these issue's?