-
Notifications
You must be signed in to change notification settings - Fork 41
Conversation
Travis automatic deployment: |
I get |
What about 12.18? |
Which files are different? All of them or main.js? |
I had a custom config. Without that, and on node
Actually, dir contents are identical (I had a white space at the end) |
I did also had a custom config! without it, I've got the same hash as @alfetopito Used node
Edit: @Velenir I've got also |
I removed everything extra and GOT IT!! |
package.json
Outdated
@@ -4,6 +4,9 @@ | |||
"description": "", | |||
"main": "src/index.js", | |||
"sideEffects": false, | |||
"engines": { | |||
"node": ">=v12.13.0 <13" |
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.
Theoretically, we work with other versions of node. The version thing is only relevant for the hash, or does it have any other value to enforce it?
Since node LTS is version 12 now, it might be ok, and even reduce chances of people running into issues
What do you think?
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.
In any case, why you enforce v12.13
?
If we do enforce, any v12
one would suffice. I've actually tested v12.1
and I get the same hash: #1095 (comment)
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.
Only relevant for hash, but it won't allow to run any script, including yarn build
on wrong version
I quickly copied from here, but we can just stick to 12
, will change
@@ -188,6 +188,7 @@ module.exports = ({ stats = false } = {}) => ({ | |||
}), | |||
].filter(Boolean), | |||
optimization: { | |||
moduleIds: 'hashed', |
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.
I'm fine with this change, although I think it was not affecting.
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.
Yep, doesn't affect, will remove
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.
Wait, it changed for me. Got QmdMLvyxKWSwvsKCLVhS2AgTWn9E91iU37xPJQMmoWRpdc
Try yarn build && ipfs add -rn dist
a couple times with moduleIds: 'hashed',
commented out
@@ -102,7 +105,7 @@ | |||
"eslint-plugin-react-hooks": "^4.0.0", | |||
"eslint-utils": ">=2.0.0", | |||
"favicons-webpack-plugin": "^3.0.1", | |||
"file-loader": "^5.0.2", | |||
"file-loader": "^6.0.0", |
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.
Is this related somehow?
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.
No, I was just updating webpack related stuff and left this in
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.
Also file-loader
switched to md4
for caching in v6, which matches webpack default
Sorta fix, please try on different machines on node v12
IPFS hash of
dist
QmNc3PH6sup1S324Vy7n45c7PEUyT71xWuFQpytmBxbM9YQmcyAq4hcixRUN7HTKf2jXD37HpHBSoauvPDGygJqGixkh
My
ls -1 dist/
List