-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pinned packages needed to build screeps node packages #34
Comments
while running under windows without docker I needed to add |
Something else seems to be breaking it again, I have the listed
Tried to just pin |
I was successful with the following pinnedPackages:
|
If I add to config.yml:
It seems to successfully build I am using the docker-compose.yml and instructions as found in the github website on a Debian12 container under proxmox. EDIT: Everything seems to compile if I use the first suggestion:
|
Update config.sample.yml with pinnedPackages and include breadcrumbs pointing at ways to fix if they change in the future: screepers#34
Update config.sample.yml with pinnedPackages and include breadcrumbs pointing at ways to fix if they change in the future: #34
Some direct dependencies seem to have been pushed with new requirements of their own dependencies, even though versions of the directs didn't change. That resulted in cacache 16.1.3 requiring ssri 9.0.0. And some others started requiring node >= 14. Strange. The following worked for me if anyone is up for reproducing and confirming?
|
thats node requiring v14.17.0 for the optional chaining operator, so maybe a slightly earlier version of minipass is needed? Any way to make sure it pulls an earlier version? |
There has been a code change in @screeps/engine^4.2.18 that tries to import a non-existent I've now gotten past this error by configuring pinnedPackages:
- '@screeps/engine^4.2.16'
... |
New version of |
Currently,
pinnedPackages
configuration is needed to get the screeps packages built successfully by launcher, due to upstream packages releasing versions that break compatibility with node 12.Creating this issue as a place to collect the needed pins and add to it as necessary.
Known necessary pins so far (see #33)
The text was updated successfully, but these errors were encountered: