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

Node 18+ updates #84

Merged
merged 31 commits into from
Apr 19, 2023
Merged

Node 18+ updates #84

merged 31 commits into from
Apr 19, 2023

Conversation

fajar-apri-alaska
Copy link
Contributor

@fajar-apri-alaska fajar-apri-alaska commented Apr 14, 2023

Alaska Airlines Pull Request

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Resolves: #63, #61, #62, #64, #65, #66, #68, #69, #70

Summary:

...

Type of change:

  • Revision of an existing capability

Checklist:

  • My update follows the CONTRIBUTING guidelines of this project
  • I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.

Thank you for your submission!

-- JetStream Design System Team

@fajar-apri-alaska fajar-apri-alaska self-assigned this Apr 14, 2023
@fajar-apri-alaska fajar-apri-alaska linked an issue Apr 14, 2023 that may be closed by this pull request
@CLAassistant
Copy link

CLAassistant commented Apr 14, 2023

CLA assistant check
All committers have signed the CLA.

@fajar-apri-alaska fajar-apri-alaska changed the title perf(husky): Pre-commit and husky update #63 Node 18+ updates Apr 14, 2023
This was linked to issues Apr 14, 2023
@blackfalcon blackfalcon self-requested a review April 14, 2023 19:12
@blackfalcon blackfalcon force-pushed the fajarapri/node18update branch from c08a6f7 to 2a9db8b Compare April 14, 2023 19:16
lines: 80
}
}
};
Copy link
Member

Choose a reason for hiding this comment

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

Please always add a new line at the end of the file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will do, thanks for the reminder.

]
};

export default [modernConfig];
Copy link
Member

Choose a reason for hiding this comment

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

Please always have a new line at the end of a file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will do, thanks for the reminder.

@fajar-apri-alaska
Copy link
Contributor Author

Hi @blackfalcon, the "Test and publish" check is failing again, I did npm install in latest node 18.
Any other configuration that is missing from my side?

@blackfalcon
Copy link
Member

Hi @blackfalcon, the "Test and publish" check is failing again, I did npm install in latest node 18. Any other configuration that is missing from my side?

When running into these issues, please review the error logs in the actions UI. This is the issue.
https://github.com/AlaskaAirlines/auro-header/actions/runs/4719720581/jobs/8370882711#step:4:17

This is the fix
https://github.com/AlaskaAirlines/auro-header/actions/runs/4719720581/jobs/8370882711#step:4:29

You should have also seen this in your localhost logs.

@blackfalcon
Copy link
Member

@fajar-apri-alaska I see that you are adding the links to the issues in progress in the PR message itself, please also add these references in the DEVELOPMENT section of the PR as well.

Screen Shot 2023-04-17 at 7 45 50 AM

@blackfalcon
Copy link
Member

@fajar-apri-alaska it's important that you add the correct information into the body of the commit message. The following commit is missing the BREAKING CHANGE message that it requires.

Screen Shot 2023-04-17 at 10 00 02 AM

Please see this example from auro-badge.
AlaskaAirlines/auro-badge@2812f8d

@fajar-apri-alaska fajar-apri-alaska linked an issue Apr 18, 2023 that may be closed by this pull request
src/auro-header.js Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
tsconfig.json Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug_report.yml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/general-support.yml Outdated Show resolved Hide resolved
src/style-fixed.scss Outdated Show resolved Hide resolved
@blackfalcon blackfalcon force-pushed the fajarapri/node18update branch 2 times, most recently from f643658 to 0989708 Compare April 18, 2023 21:26
The following outlines the steps needed for updating any repo to the latest version of Husky.

- npx husky-init
- npm i @open-wc/testing@latest @web/test-runner@latest @web/dev-server@latest --save-dev
- npm run prepare
- chmod ug+x .husky/*
- chmod ug+x .git/hooks/*
- Update package.json - "test": "wtr --coverage", and "test:watch": "wtr --watch",
- Add web-test-runner.config.mjs
- Update .husky/pre-commit and necessary pre-commit actions
- Delete legacy Husky configs from package.json
- Delete karma.conf.js file
- Uninstall @open-wc/testing-karma

Changes to be committed:
	new file:   .husky/pre-commit
	deleted:    karma.conf.js
	modified:   package-lock.json
	modified:   package.json
	new file:   web-test-runner.config.mjs
Changes to be committed:
	modified:   README.md
	deleted:    babel.config.js
	modified:   package-lock.json
	modified:   package.json
	deleted:    rollup.config.js
	new file:   rollup.config.mjs
	deleted:    src/es5.js
Changes to be committed:
	modified:   .github/workflows/testPublish.yml
	modified:   package-lock.json
	modified:   package.json
	modified:   src/style-fixed.scss
	modified:   src/style.scss
@blackfalcon blackfalcon force-pushed the fajarapri/node18update branch from 062ddb4 to c5786a1 Compare April 19, 2023 17:18
This commit removes legacy content from current resources
and deleted files that are no longer required.

Changes to be committed:
modified:   README.md
deleted:    demo/alert.js
modified:   demo/index.html
deleted:    demo/index_old.html
deleted:    demo/sass/style.scss
deleted:    polymer.json
Changes to be committed:
modified:   package-lock.json
modified:   package.json
Changes to be committed:
modified:   package.json
Changes to be committed:
deleted:    scripts/postinstall.js
Changes to be committed:
modified:   .github/ISSUE_TEMPLATE/general-support.yml
Changes to be committed:
modified:   package.json
@blackfalcon blackfalcon marked this pull request as ready for review April 19, 2023 17:49
@blackfalcon blackfalcon requested a review from a team as a code owner April 19, 2023 17:49
@blackfalcon blackfalcon self-requested a review April 19, 2023 17:49
blackfalcon
blackfalcon previously approved these changes Apr 19, 2023
Changes to be committed:
deleted:    index.html
@blackfalcon blackfalcon merged commit 0dfce2f into master Apr 19, 2023
@blackfalcon blackfalcon deleted the fajarapri/node18update branch April 19, 2023 18:00
@blackfalcon
Copy link
Member

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@blackfalcon blackfalcon added the released Completed work has been released label Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment