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

Update all examples #626

Merged
merged 2 commits into from
Aug 4, 2020
Merged

Update all examples #626

merged 2 commits into from
Aug 4, 2020

Conversation

j0k3r
Copy link
Member

@j0k3r j0k3r commented Jul 31, 2020

What did you implement:

I updated all examples to latest deps & version.
They should all run properly and be up to date.

I've removed some of them because there weren't accurate as of today.

I've also updated the Travis build:

  • Avoid double build when PR is created on upstream (a build for PR and one for push).
  • Only run coverage one build (and send coverage only once instead of twice). Also don't run coverage on Appveyor as we don't use it.

Note: I targeted master so dependabot PR will be closed automatically after merging that PR.
Note 2: lot of diff stuff but mostly due to lock files being updated.

Todos:

  • Write tests
  • Write documentation
  • Fix linting errors
  • Make sure code coverage hasn't dropped
  • Provide verification config / commands / resources
  • Enable "Allow edits from maintainers" for this PR
  • Update the messages below

Is this ready for review?: YES
Is it a breaking change?: NO

j0k3r added 2 commits July 31, 2020 08:54
So they are up to date with deps and they are all working (for sure: I've tested them one by one)

Upgrade `"serverless-webpack": "file:../..",` to `"serverless-webpack": "^5.3",` because each test resulted in `Error: Cannot find module 'webpack'` ... (only with NPM not with Yarn)

- remove outdated `babel` example because it use webpack 3 and it's superseded by `babel-webpack-4`
- remove `serverless-offline` example as other one already use serverless-offline
- update all examples to latest deps version
Avoid double build when PR is created on upstream (a build for PR and one for push).
Only run coverage one build (and send coverage only once instead of twice). Also don't run coverage on Appveyor as we don't use it.
@j0k3r j0k3r added this to the 5.3.4 milestone Jul 31, 2020
# avoid double Travis build when the PR is created on upstream
if: |
type = pull_request OR \
branch = master
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't we run builds on master to make sure it build properly? Some repositories treat master as unstable, but not sure whether we are doing that for this repo.

@@ -6,7 +6,7 @@ plugins:

provider:
name: aws
runtime: nodejs6.10
runtime: nodejs12.x
Copy link
Member

Choose a reason for hiding this comment

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

Nice. Thanks!

Copy link
Member

@miguel-a-calles-mba miguel-a-calles-mba left a comment

Choose a reason for hiding this comment

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

Thanks! I tried using the examples on a project recently and couldn't get them to work.

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.

2 participants