Skip to content
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

init: atomic-browser at 0.37.0 #164

Closed
wants to merge 1 commit into from

Conversation

albertchae
Copy link
Contributor

@albertchae albertchae commented Mar 6, 2024

The next step of #15

  • Use pnpm2nix-nzbr which supports pnpm version 6 lockfiles.
  • Because atomic-browser is using pnpm workspaces, installInPlace and distDir="."

A follow up PR will create a module for this

Co-authored-by: Anish Lakhwara [email protected]

Copy link
Contributor

github-actions bot commented Mar 6, 2024

No difference in nix flake show.

1 similar comment
Copy link
Contributor

github-actions bot commented Mar 6, 2024

No difference in nix flake show.

@albertchae albertchae force-pushed the moss/atomix-browser-pnpm-nzbr branch from 13fa66c to 4b6f3e2 Compare March 6, 2024 05:15
Copy link
Contributor

github-actions bot commented Mar 6, 2024

No difference in nix flake show.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tried to make this file follow the format of all the others since it appears they were standardized at some point

pkgs/by-name/atomic-browser/package.nix Show resolved Hide resolved
albertchae added a commit to ngi-nix/atomic-server that referenced this pull request Mar 6, 2024
…uses one typescript version (5.3.2)

We came across this while working on ngi-nix/ngipkgs#164.
While not strictly necessary for that task, it seemed like it was unintentional
that the project was depending on different versions of typescript (PR with original
upgrade is atomicdata-dev#710), so
I removed typescript in the various subdirectories so they all depend
on the same version as root.

- Edit tsconfig.build.json to fix the following error
  `TS5110: Option 'module' must be set to 'NodeNext' when option 'moduleResolution' is set to 'NodeNext'.`

- All the removed packages from pnpm-lock.yaml are duplicate entries
Copy link
Contributor

@Chickensoupwithrice Chickensoupwithrice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Build works for me too.

- Use pnpm2nix-nzbr which supports pnpm version 6 lockfiles.
- Because atomic-browser is using pnpm workspaces, `installInPlace` and `distDir="."`

A follow up PR will create a module for this

Co-authored-by: Anish Lakhwara <[email protected]>
@albertchae albertchae force-pushed the moss/atomix-browser-pnpm-nzbr branch from 4b6f3e2 to 2015a5d Compare March 7, 2024 09:16
Copy link
Contributor

github-actions bot commented Mar 7, 2024

No difference in nix flake show.

@albertchae
Copy link
Contributor Author

This is failing CI because the builder we introduced (https://github.com/nzbr/pnpm2nix-nzbr/) is using IFD. We are exploring alternatives

@fricklerhandwerk
Copy link
Collaborator

Discussed with @albertchae and @Chickensoupwithrice

Closing in favor of #170

@albertchae albertchae deleted the moss/atomix-browser-pnpm-nzbr branch June 10, 2024 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants