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

refactor: cleanup buildbot_build_go_functions, zisi_parse_isc and buildbot_nft_transpile_esm` feature flags #4325

Merged
merged 2 commits into from
Jun 24, 2022

Conversation

danez
Copy link
Contributor

@danez danez commented Jun 15, 2022

All 3 ff are now always on

Requires netlify/zip-it-and-ship-it#1113

@danez danez added the type: chore work needed to keep the product and development running smoothly label Jun 15, 2022
@danez
Copy link
Contributor Author

danez commented Jun 17, 2022

After updating to zisi 5.11 with FF zisi_detect_esm being removed there lots of tests fail here. This happens because the default here was false for this flag (or undefined).

When this FF is now finally turned on for the tests (because it is removed), zisi is using the nft-bundler for esm modules instead of the zisi-bundler previously.
This somehow behaves a lot different and seems to throw a lot less errrors.

One example:

import mathAvg from 'math-avg-mispelled'

export default () => mathAvg([])

Previously (with zisi-bundler) it failed because the dependency is not found.
Now (with nft-bundler) it works perfectly fine. No error whatsoever.

Is this expected? cc @Skn0tt @eduardoboucas

@eduardoboucas
Copy link
Member

Hmm, we've been using NFT for ESM functions for a while now, and maybe we just didn't update the Netlify Build tests accordingly at the time. I think this is okay.

…ldbot_nft_transpile_esm` ff

All 3 are now always on

fix(deps): update @netlify/zip-it-and-ship-it to 5.11.0

chore: fix tests
@danez danez marked this pull request as ready for review June 23, 2022 09:34
@danez danez requested a review from a team June 23, 2022 09:34
}

const PACKAGE_JSON_ORIGINAL_MESSAGE = 'is invalid JSON'
const PACKAGE_JSON_ORIGINAL_MESSAGES = ['is invalid JSON', 'in JSON at position']
Copy link
Member

Choose a reason for hiding this comment

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

Hmm in JSON at position feels a bit too broad, but I guess there's no better way to catch there errors?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah i tried to match as a much as possible, but there is not much. The whole error is SyntaxError: Unexpected token { in JSON at position 1

Copy link
Member

@eduardoboucas eduardoboucas left a comment

Choose a reason for hiding this comment

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

🚀

@danez danez merged commit 9a25714 into main Jun 24, 2022
@danez danez deleted the ff_cleanup branch June 24, 2022 11:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: chore work needed to keep the product and development running smoothly
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants