-
Notifications
You must be signed in to change notification settings - Fork 15
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
fix: css styles applied & config page collapse #112
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self review
it('has css file with expected content', async () => { | ||
await expect(access(resolve(cwd, '../dist/ipfs-sw-styles.css'), constants.F_OK)).to.not.be.rejected() | ||
const contents = await readFile(resolve(cwd, '../dist/ipfs-sw-styles.css'), 'utf8') | ||
expect(contents).to.include('47vh') | ||
expect(contents).to.include('.local-storage-toggle input.status') | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we will likely want to remove this in the future but i'm going to leave it for now
"sideEffects": [ | ||
"*.css" | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needed this to tell webpack about our css (tree splitting was ignoring css files because we told it we had no side effects..).
IIUC this is a webpack specific thing. see https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free
Title
Fix css styles not being included in final assets & better config page handling
Description
If a user explicitly wants to see the config from the subdomain, it should not be collapsed by default. Will update shortly.This will be done in a separate PR. see feat: explicit subdomain request to view config page should not be collapsed by default #113fixes #111
Notes & open questions
Change checklist