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

Move all build tooling into one system #2167

Closed
Shelob9 opened this issue Dec 20, 2017 · 0 comments
Closed

Move all build tooling into one system #2167

Shelob9 opened this issue Dec 20, 2017 · 0 comments
Assignees
@Shelob9
Labels
enhancement New feature
Milestone
1.7.0

Comments

@Shelob9
Copy link
Collaborator

Shelob9 commented Dec 20, 2017

Currently we have grunt for release builds and JS/CSS builds. And webpack for the block build, and webpack for the cf-pro client build.

Either the block build or the webpack build should become the one true build process.

I'm putting this on 1.5.8 but may punt as I have to finish thinking through blocks first.
@Shelob9 Shelob9 added the enhancement New feature label Dec 20, 2017
@Shelob9 Shelob9 added this to the 1.5.9 milestone Dec 20, 2017
@Shelob9 Shelob9 self-assigned this Dec 20, 2017
@Shelob9 Shelob9 mentioned this issue Dec 20, 2017
Closed
@Shelob9 Shelob9 mentioned this issue Jan 3, 2018
Closed
@Shelob9 Shelob9 modified the milestones: 1.5.9, 1.6.0 Jan 6, 2018
@Shelob9 Shelob9 mentioned this issue Feb 28, 2018
Merged
@Shelob9 Shelob9 mentioned this issue Mar 14, 2018
Open
This was referenced Apr 5, 2018
Closed
Closed
Shelob9 pushed a commit that referenced this issue Apr 14, 2018
begin webpack config and move block build to new webpack #2167
fe566c5
@Shelob9 Shelob9 mentioned this issue Apr 16, 2018
Closed
Shelob9 pushed a commit that referenced this issue Apr 17, 2018
rough in all entry points #2167
5a7205b
Shelob9 pushed a commit that referenced this issue Apr 17, 2018
#2167 move fields file to webpack build
b612fd7
Shelob9 pushed a commit that referenced this issue Apr 17, 2018
make work without using webpack for admin or editor #2167
b317fce
Shelob9 pushed a commit that referenced this issue Apr 17, 2018
#2167 put roadmap in readmes
6792fc6
@Shelob9 Shelob9 mentioned this issue Apr 19, 2018
Merged
2 tasks
Shelob9 pushed a commit that referenced this issue Apr 19, 2018
move editor to client #2167 I might back out of this, balrickTriggers…
829d23b 
… do not work yet
Shelob9 pushed a commit that referenced this issue Apr 19, 2018
Revert "move editor to client #2167 I might back out of this, balrick…
dfe1a10 
…Triggers do not work yet"

This reverts commit 829d23b.
Shelob9 pushed a commit that referenced this issue Apr 19, 2018
add back in the readme for functions dir #2167
c303284
Shelob9 pushed a commit that referenced this issue Apr 19, 2018
#2167 update build script
3ba402e
Shelob9 pushed a commit that referenced this issue Apr 19, 2018
#2167 document npm commands in readme
361caae
Shelob9 pushed a commit that referenced this issue Apr 19, 2018
#2167 enqueue form css on main admin page so forms look right in the …
e95f830 
…entry editor
Shelob9 pushed a commit that referenced this issue May 9, 2018
fix parts of #2167 that got lost in merge
65ce3a5
Shelob9 pushed a commit that referenced this issue May 9, 2018
rm old package.json #2167
cd28843
@Shelob9 Shelob9 mentioned this issue May 24, 2018
Closed
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Shelob9 Shelob9

Labels
enhancement New feature
Projects
None yet
Milestone
1.7.0
Development

No branches or pull requests
1 participant
@Shelob9