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

Local development issue #234

Closed
ugogo opened this issue Nov 24, 2016 · 11 comments
Closed

Local development issue #234

ugogo opened this issue Nov 24, 2016 · 11 comments
Assignees
Milestone

Comments

@ugogo
Copy link

ugogo commented Nov 24, 2016

Bug Report

  • Package version(s): 1.1.0
  • Browser and OS versions: Chrome OSX

Describe the issue:

Hey guys 👋

I just cloned your project and tried to submit my first PR, but I ran into an issue : local changes doesn't change anything into the local server.

What did I do?
  • git clone https://github.com/palantir/blueprint.git && cd blueprint
  • npm install && npm run bootstrap && npm run gulp as said into the README
  • Navigate to localhost:9000/packages/docs/dist/
  • Add display: none !important; (just for a very basic test) into packages/core/src/components/callout/_callout.scss

Actual behavior:

The page reload (http://localhost:9000/packages/docs/dist/#components.callout), but callouts are still visible, and no sign of my change into the Chrome devtools.

Expected behavior:

Changes taken into account.

I'm apparently missing something, if anyone can help me,
Thanks 🙏

@llorca llorca added this to the 1.2.0 milestone Nov 24, 2016
@llorca
Copy link
Contributor

llorca commented Nov 24, 2016

I can repro on my end. We'll get to this ASAP

@giladgray
Copy link
Contributor

giladgray commented Nov 24, 2016 via email

@adidahiya
Copy link
Contributor

what's the output in your gulp console? is it picking up the .scss changes and re-bundling the docs application?

@ugogo
Copy link
Author

ugogo commented Nov 25, 2016

@giladgray Even if I reload the page myself, there's no change.
@adidahiya : I recorded my screen, this should help you to learn more about it : https://www.dropbox.com/s/5jrxnguraf8hzu1/blueprint-local-dev-issue.mov?dl=0

@adidahiya adidahiya removed this from the 1.2.0 milestone Nov 25, 2016
@adidahiya adidahiya added this to the 1.2.0 milestone Nov 28, 2016
@ugogo
Copy link
Author

ugogo commented Dec 1, 2016

Can I provide you more informations to help you?

@giladgray
Copy link
Contributor

@ugogo it seems like livereload does not work for individual packages, but it does work for the docs package itself. try saving docs.scss after editing _callout.scss and see if that causes your changes to appear in the browser.

@ugogo
Copy link
Author

ugogo commented Dec 2, 2016

@giladgray Still no changes.

Maybe those leads can help you :

Leads 1 - I removed everything into docs.scss and blueprint.scss, and nothing changes too. Then, I tried npm run gulp sass manually, and with it, I had some warnings ('files cannot be empty', yey!)

Leads 2 - I removed the docs/docs/docs.css file, reloaded the page, the style was well removed. But, even after relaunching npm run gulp, the dist CSS was not re-generated.

@giladgray
Copy link
Contributor

are you actually looking at localhost:9000/packages/docs/dist/?
as opposed to localhost:9000/docs/, which is the compiled GHPages site and is not updated during development (only npm run build:site).

@ugogo
Copy link
Author

ugogo commented Dec 2, 2016

Hah nice catch for this one.
Running manually npm run gulp sass did update the CSS for localhost:9000/packages/docs/dist!

@ugogo
Copy link
Author

ugogo commented Dec 2, 2016

Ok, I added sass after sass-variables here: https://github.com/palantir/blueprint/blob/master/gulp/watch.js#L23, it works.
But I don't think it's a good idea, and if the linter throw an error, there's no coming back \o/

@llorca llorca modified the milestones: 1.2.0, 1.3.0 Dec 2, 2016
giladgray pushed a commit that referenced this issue Dec 6, 2016
docs.scss imports all the compiled CSS files, which then get processed into docs.css. Changing a downstream package SCSS file (like `_buttons.scss`) updates blueprint.css but docs.scss does not pick up those changes.

this refactors sass and typescript watching to actually ignore generated files and adds a watcher that recompiles docs.scss when any dist/*.css file changes.

fixes #234
adidahiya pushed a commit that referenced this issue Dec 7, 2016
docs.scss imports all the compiled CSS files, which then get processed into docs.css. Changing a downstream package SCSS file (like `_buttons.scss`) updates blueprint.css but docs.scss does not pick up those changes.

this refactors sass and typescript watching to actually ignore generated files and adds a watcher that recompiles docs.scss when any dist/*.css file changes.

fixes #234
@ugogo
Copy link
Author

ugogo commented Dec 8, 2016

Thanks guys 👍

greglo pushed a commit to greglo/blueprint that referenced this issue Dec 12, 2016
docs.scss imports all the compiled CSS files, which then get processed into docs.css. Changing a downstream package SCSS file (like `_buttons.scss`) updates blueprint.css but docs.scss does not pick up those changes.

this refactors sass and typescript watching to actually ignore generated files and adds a watcher that recompiles docs.scss when any dist/*.css file changes.

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

No branches or pull requests

5 participants