Bug: Build artifact at Beta 6 is different from `npm run build`
See original GitHub issue// `npm run build` output dist/index.cjs
'use strict';
exports = module.exports = fetch;
function fetch(url, options_) {
// ...
}
vs
// published 3.0.beta-6 dist/index.cjs
'use strict';
exports = module.exports = fetch;
const fetch = (url, options_) => {
// ..
}
//
Not sure if there is an extra pre-publishing step performed, but as a result beta.6
is completely broken.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
[BUG] Preinstall script runs after installing dependencies #2660
Current Behavior: In NPM v7 the preinstall script runs after dependencies are installed, which breaks backwards compatibility with NPM v6.
Read more >Code build is failed with Error while executing command: npm ...
I assigned the administration access temporarily and it worked but failed due to different reason. To check it, try to execute the simple...
Read more >How to Automate NPM Package Publishing With Azure ...
Step 1: Authorize Azure Pipelines. Link to this section · Step 2: Build pipeline · Step 3: Release pipeline · Step 4: Publish...
Read more >Postinstall-build - npm.io
This example is missing a build artifact – or rather, npm run build is mistakenly being passed as the build artifact. Since that...
Read more >npm-publish - npm Docs
This can be overridden by specifying a different default registry or using a scope ... [--dry-run] : As of npm@6 , does everything...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@xxczaki the issue wasn’t related to Rollup - it can export as an arrow function. The problem was that by changing from a
function
toconst
you break the hoisting, so,fetch
becomes undefined on top of the file.That was a huge PR, changing across 12 files and merged after just one approval - we should set policy on that…