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

Fix packages #649

Merged
merged 12 commits into from
Mar 30, 2023
Merged

Fix packages #649

merged 12 commits into from
Mar 30, 2023

Conversation

m1ga
Copy link
Contributor

@m1ga m1ga commented Mar 24, 2023

after weeks of testing I found that babel was the issue!

  • using fixed packages
  • fixed (old) babel version
  • fixed tests

Use Squash & Merge to reduce the test commit logs

Copy link
Contributor

@cb1kenobi cb1kenobi left a comment

Choose a reason for hiding this comment

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

I did a code review and it looks fine, however testing this is nearly impossible. Overwriting the node-titanium-sdk in the SDK before or after build is a lot of work. I tried and I still see the error, so something isn't right.

So, I'm going to approve this, merge it, ship a new node-titanium-sdk. Then we can properly test the SDK. If it doesn't fix the callsite issue, then we can iterate until we do fix it.

@cb1kenobi cb1kenobi merged commit 144df9c into tidev:master Mar 30, 2023
@m1ga
Copy link
Contributor Author

m1ga commented Mar 30, 2023

I'll do some tests later. I always used npm i with the github branch to do my tests. That way you can test it before it was released. But still: was very pailful to do it and took very long, so hopefully this fixes it 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants