Release 2.0

[hildjj]

TODO list:

• Test issues #215
• Sourcemap url #218
• Look into rollup warnings #220
• source-map-generator needs to be bundled #223
• Update deps #248
• Update changelog. #254 Double-check release notes
• Version #255
• Merge 1.3 to main
• Test, including browser
• Update release date in CHANGELOG.md
• Tag
• npm publish
• Github release notes
• Announce on Twitter

Everything else that isn't a show-stopper will be pushed to 2.1, including:

• Debug helpers - new output type ast / CLI option -a/--ast #206

[hildjj]

Note: because of issues arising in #248, this is going to be a 2.0 release. Same TODO list.

[physikerwelt]

@hildjj in #244 (comment) you estimated an upper bound for the release date as June 9th. Is this correct? Would it be feasible to update the estimate here if new information is available?

[hildjj]

Keep in mind that the estimate was just an estimate, not a contract. If you'd like to help, here are a few things that will get us there more quickly:

• Look into rollup warnings #220
• Update docs for source-map-generator needs to be bundled #223
• An example that shows the sourcemap'd output working in the browser debugger (to ensure that the code that adds the sourcemapURL is correct)
• Check all of the PRs since 1.2 to make sure they are adequately reflected in the release notes

[physikerwelt]

Thank you. I think I am not familiar enough with the code to be a great help here.

Check all of the PRs since 1.2 to make sure they are adequately reflected in the release notes

At least this is definitely not the case, but I do not understand enough to make a reasonable pull request, sorry.

[hildjj]

I think we should push #206 to the next release. That leaves reviews needed for #251 and #252, then release engineering.

[hildjj]

This release should go out within the hour. Final release engineering in progress.

[hildjj]

Leaving this open in case there are nits. For example, I didn't add the date to the changelog. :(

[physikerwelt]

Thank you @hildjj . I did run the upgrade and realized that there are a few duplicated rules. In my case, there were 151 functions before and now there are 203. Sometimes the exact same functions follow each other. Eventually, all tests still pass so this might only be a cosmetic issue, but it would feel good to understand this change.

[hildjj]

Can you point out the line numbers of a couple of the dups please? I bet you have them right in front of you, and that way I won't have to go through the whole diff.

[physikerwelt]

The link should point to the first difference. Unfortunately, the diff viewer can not handle whitespace so well. That is how it looks in my Firefox:

[hildjj]

Let's start a new issue for this, I think? We'll need to do some analysis and brainstorming of solutions.

[physikerwelt]

Ok, will do. I was hoping for another answer;-)

[hildjj]

@Mingun might just be able to tell by looking at it. :)

[Mingun]

This is because now we can generate a source map and should map each function to a different location in the source .peggy

[hildjj]

If anyone has more issues with the release, take them to #268, please.