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.

Sign up for GitHub

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

Jump to bottom

Plan for better developer tooling #198

Closed
ecaldwell opened this issue Aug 9, 2017 · 5 comments
Closed

Plan for better developer tooling #198

ecaldwell opened this issue Aug 9, 2017 · 5 comments

Comments

@ecaldwell
Copy link
Contributor

ecaldwell commented Aug 9, 2017 •
edited
Loading

The fix proposed in #197 uses features of ES2015. To maintain support of this app in legacy browsers (looking at you IE11) main.js needs to be transpiled with babel during the build process. I thought this might be an opportune time to review and modify the overall developer tooling in this project since it has been brought up in many other issues (e.g. #113, #176, #178).

I'll throw some of the initial ideas down as their own comments so they can be voted on. Feel free to add your own ideas.
@ecaldwell
Copy link
Contributor Author

Run babel on main.js

@ecaldwell
Copy link
Contributor Author

Replace Grunt with vanilla npm scripts

@ecaldwell
Copy link
Contributor Author

Webpack

@ecaldwell
Copy link
Contributor Author

Build JSAPI with Bower

@ecaldwell
Copy link
Contributor Author

Incorporate Prettier. Ideally, this should be triggered before Pull Requests.

@ecaldwell ecaldwell mentioned this issue Sep 1, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ecaldwell