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

docs(getting-started): mention importing hammer in same file as bootstrap #6225

Merged
merged 2 commits into from
Aug 4, 2017
Merged

docs(getting-started): mention importing hammer in same file as bootstrap #6225

merged 2 commits into from
Aug 4, 2017

Conversation

cyrilletuzi
Copy link
Contributor

As mentioned in #308, if hammerjs is imported in AppModule, Universal server-side rendering will fail as hammerjs is a browser specific library using window, document... So it must be imported in browser entry point src/main.ts instead.

As mentioned in #308, if hammerjs is imported in AppModule, Universal server-side rendering will fail as hammerjs is a browser specific library using window, document... So it must be imported in browser entry point src/main.ts instead.
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 2, 2017
@@ -113,7 +113,7 @@ To install via npm, use the following command:
npm install --save hammerjs
```

After installing, import it on your app's root module.
After installing, import it on your app's entry point (`src/main.ts`).
Copy link
Member

Choose a reason for hiding this comment

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

I'd add an e.g., before the filename to make it more clear that it's an example and that not everyone will necessarily have this file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

As mentioned in #308, if hammerjs is imported in AppModule, Universal server-side rendering will fail as hammerjs is a browser specific library using window, document... So it must be imported in browser entry point src/main.ts instead.
@jelbourn jelbourn added docs This issue is related to documentation pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 4, 2017
@jelbourn jelbourn changed the title docs(hammerjs): new import location for Universal docs(getting-started): mention importing hammer in same file as bootstrap Aug 4, 2017
@tinayuangao tinayuangao merged commit 1af2ce6 into angular:master Aug 4, 2017
crisbeto pushed a commit to crisbeto/material2 that referenced this pull request Aug 5, 2017
…trap (angular#6225)

* docs(hammerjs): new import location for Universal

As mentioned in angular#308, if hammerjs is imported in AppModule, Universal server-side rendering will fail as hammerjs is a browser specific library using window, document... So it must be imported in browser entry point src/main.ts instead.

* docs(hammerjs): new import location for Universal

As mentioned in angular#308, if hammerjs is imported in AppModule, Universal server-side rendering will fail as hammerjs is a browser specific library using window, document... So it must be imported in browser entry point src/main.ts instead.
@cyrilletuzi cyrilletuzi deleted the patch-1 branch August 19, 2017 12:48
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement docs This issue is related to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants