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

Cross-origin isolation support in Chrome #67

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

frantic0
Copy link

@frantic0 frantic0 commented Jul 28, 2021

Closes #66

package-lock.json Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
src/index.js Show resolved Hide resolved
@@ -8,7 +8,32 @@ export default {
format: 'cjs',
},
plugins: [
serve({ contentBase: '', port: Math.round(Math.random() * 10000) + 40000 }),
live(),
serve({
Copy link
Owner

Choose a reason for hiding this comment

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

Do you have an idea of how to test this in CI?

Copy link
Author

@frantic0 frantic0 Aug 2, 2021

Choose a reason for hiding this comment

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

hi @thgh, do you mean testing plugin serve with that specific configuration?

I suppose we could set GH actions with node.js to capture the output of rollup.

Would you require this to approve this PR? I see that there is no CI setup in place yet.

Copy link
Author

Choose a reason for hiding this comment

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

Had a peek at how node-livereload does the server testing.

https://github.com/frantic0/node-livereload/blob/main/test/index.test.coffee

It is a travis CI setup and does include server configurations

Copy link
Owner

Choose a reason for hiding this comment

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

No requirement, just looking for inspiration

I'm not using this plugin actively so we should start doing automated testing to remain confident when releasing. I hope to make it a requirement soon.

removed and installed livereload to latest
Copy link
Author

@frantic0 frantic0 left a comment

Choose a reason for hiding this comment

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

@thgh, thanks for the review, just pushed the changes

@@ -8,7 +8,32 @@ export default {
format: 'cjs',
},
plugins: [
serve({ contentBase: '', port: Math.round(Math.random() * 10000) + 40000 }),
live(),
serve({
Copy link
Author

@frantic0 frantic0 Aug 2, 2021

Choose a reason for hiding this comment

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

hi @thgh, do you mean testing plugin serve with that specific configuration?

I suppose we could set GH actions with node.js to capture the output of rollup.

Would you require this to approve this PR? I see that there is no CI setup in place yet.

@jonkoops
Copy link
Collaborator

@frantic0 thanks for the PR. Could you rebase it and fix the merge conflicts?

@thgh
Copy link
Owner

thgh commented Aug 15, 2023

This PR depends on an open PR in livereload: napcs/node-livereload#155

To land this, we will need patch-package or a published fork of livereload

@jonkoops
Copy link
Collaborator

Hmmm, yeah. Let's try to reach out to @napcs to see if he might need some help with maintenance. I think we will try to get to this once we have things moved to the Rollup repos (see #87).

@napcs
Copy link

napcs commented Sep 22, 2023

👋 I have this PR for LiveReload that addresses CORS and CORP - it's a different one than you referenced here.napcs/node-livereload#164

Would this be adequate for what you need?

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.

Cross-origin isolation support for Chrome
4 participants