-
Notifications
You must be signed in to change notification settings - Fork 35
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
Remove decorators #94
Conversation
This reverts commit a567dd9.
+1 on merging this if possible. This patch unblocked us. Thanks @mhluska |
The referenced issue was actually related to a build time bug, which affected multiple projects in the Ember ecosystem and has been patched. You should be able to fix the issue by running Decorators have been stable for some time, and native class syntax is the future direction for Ember as a whole. |
We are using NPM on our project. I am not seeing an update in our package-lock.json when clean-reinstalling our project dependencies, even after clearing my local cache. What do you think we are missing? |
I'm not too sure as I don't have much experience with NPM lockfiles. You should be able to check to see if the build dependency has updated though. The affected version was |
@pzuraq I'm totally fine with keeping yarn. I've reverted those changes. |
Sorry for the delay life has been absurdly busy lately. I'm generally 👍 on this change. Exploring decorators has been interesting, but feels like it has caused more issues than it has solved. In the long-term, I'm much more interested in using Typescript over decorators. I want to give this a slightly more thorough lookover in the next few days before merging. |
I was having some issues in my app related to decorators. I realized this is the only dependency in my tree relying on them. I started to think that it's somewhat strange to require them in a library that others might use as a building block.
This also removes yarn, removes some unneeded dependencies and fixes an npm vulnerability (
npm audit fix --force
).I realize this is a pretty controversial PR and should probably be split up into smaller chunks. I can do it if needed.
I made sure tests are passing locally and I'm using this in production.