Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

66%
+2 −0
Q&A Ignore NPM Modules Digital Ocean App Platform

I solved this last night and meant to come back and update, the problem is totally mine. Jest requires a package-lock.json file in GitHub actions to run. DigitalOcean App platform checks for a Do...

posted 12mo ago by fausty‭  ·  edited 12mo ago by fausty‭

Answer
#2: Post edited by user avatar fausty‭ · 2023-04-14T17:13:31Z (12 months ago)
  • I solved this last night and meant to come back and update, the problem is totally mine.
  • Jest requires a package-lock.json file in GitHub actions to run.
  • DigitalOcean App platform checks for a Dockerfile if you have one, or package.json/ package-lock.json, it'll follow those rules and the app spec will ask you to add an output directory.
  • Since, this code is not bundled as a package, my code to run my webpage doesn't get sent to the output_dir where Digital Ocean checks for the deployment.
  • I solved this problem by not keeping a package.json files in the repo, and I have GitHub create them as a part of the action.
  • I now run this before installing dependencies and running the test in my GitHub merge request pipeline and App Platform will never see it, so it won't kick off its automated package.json processes.
  • ```
  • - name: Create package.json
  • run: |
  • echo '{
  • "name": "aphor",
  • "version": "1.0.0",
  • "description": "Randomly displays a single quote from a json collection",
  • "scripts": {
  • "test": "jest"
  • },
  • "devDependencies": {
  • "@babel/core": "^7.21.4",
  • "@babel/preset-env": "^7.21.4",
  • "babel-jest": "^29.5.0",
  • "jest-environment-jsdom": "^29.5.0",
  • "jest-fetch-mock": "^3.0.3",
  • "node-fetch": "^2.6.9"
  • }
  • }' > package.json
  • ```
  • I solved this last night and meant to come back and update, the problem is totally mine.
  • Jest requires a package-lock.json file in GitHub actions to run.
  • DigitalOcean App platform checks for a Dockerfile if you have one, or package.json/ package-lock.json, it'll follow those rules and the app spec will ask you to add an output directory.
  • Since this code is not bundled as a package, my code to run my webpage doesn't get sent to the output_dir where Digital Ocean checks for the deployment.
  • I solved this problem by not keeping a package.json files in the repo, and I have GitHub create them as a part of the action.
  • I now run this before installing dependencies and running the test in my GitHub merge request pipeline and App Platform will never see it, so it won't kick off its automated package.json processes.
  • ```
  • - name: Create package.json
  • run: |
  • echo '{
  • "name": "aphor",
  • "version": "1.0.0",
  • "description": "Randomly displays a single quote from a json collection",
  • "scripts": {
  • "test": "jest"
  • },
  • "devDependencies": {
  • "@babel/core": "^7.21.4",
  • "@babel/preset-env": "^7.21.4",
  • "babel-jest": "^29.5.0",
  • "jest-environment-jsdom": "^29.5.0",
  • "jest-fetch-mock": "^3.0.3",
  • "node-fetch": "^2.6.9"
  • }
  • }' > package.json
  • ```
#1: Initial revision by user avatar fausty‭ · 2023-04-14T17:10:01Z (12 months ago)
I solved this last night and meant to come back and update, the problem is totally mine. 

Jest requires a package-lock.json file in GitHub actions to run. 

DigitalOcean App platform checks for a Dockerfile if you have one, or package.json/ package-lock.json, it'll follow those rules and the app spec will ask you to add an output directory. 

Since, this code is not bundled as a package, my code to run my webpage doesn't get sent to the output_dir where Digital Ocean checks for the deployment. 

I solved this problem by not keeping a package.json files in the repo, and I have GitHub create them as a part of the action. 

I now run this before installing dependencies and running the test in my GitHub merge request pipeline and App Platform will never see it, so it won't kick off its automated package.json processes. 

```
      - name: Create package.json
        run: |
          echo '{
            "name": "aphor",
            "version": "1.0.0",
            "description": "Randomly displays a single quote from a json collection",
            "scripts": {
              "test": "jest"
            },
            "devDependencies": {
            "@babel/core": "^7.21.4",
            "@babel/preset-env": "^7.21.4",
            "babel-jest": "^29.5.0",
            "jest-environment-jsdom": "^29.5.0",
            "jest-fetch-mock": "^3.0.3",
            "node-fetch": "^2.6.9"
            }
          }' > package.json
```