-
-
Notifications
You must be signed in to change notification settings - Fork 96
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
elm-pages
v2.1.11 has some files in .elm-pages
and elm-stuff
created as read-only when node_modules
is read-only
#305
Comments
13 tasks
jali-clarke
added a commit
to NoRedInk/nixpkgs
that referenced
this issue
May 30, 2022
`node-packages.nix` was regenerated after having run `generate-node-packages.sh` in order to pick up dependencies for `elm-pages`. In addition, we add `elm`, `elm-review`, and `elm-optimize-level-2` to the `PATH` for `elm-pages` since those are needed at runtime. A patch is also included to fix an issue where files are copied from the `nix-store` as read-only (credit to @bcardiff for that fix). An upstream issue dillonkearns/elm-pages#305 has been opened to track this.
I'm seeing this as well with elm-pages 3.0. |
I created NixOS/nixpkgs#235300 for a more comprehensive fix. I have been thinking about making a PR to include the |
oh, also it's not against 3.0 :P |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some application deployment methods freeze
node_modules
as read-only to prevent accidental modification at application runtime. When we bundleelm-pages
@v2.1.11
using this method, it copies these files into.elm-pages
andelm-stuff
while preserving their read-only permissions. This makes it impossible to e.g. runelm-pages dev
twice without deleting.elm-pages
andelm-stuff
between invocations.The following patch fixes this for
v2.1.11
:The code in
master
has changed since then, however.The text was updated successfully, but these errors were encountered: